SAP Note FAQ: Delivery split when creating deliveries

Transcription

1 SAP Nte FAQ: Delivery split when creating Nte Language: English Versin: 2 Validity: Valid Since Summary Symptm This nte cntains answers t frequently asked questins regarding tpic delivery split fr the creatin f utbund with reference t sales rders: Questin catalg 1. Which header fields lead t a delivery split? 2. What is meant by delivery split accrding t warehuse number? 3. Why des a split ccur due t deviating partners? 4. Which fields lead t the split fr internal settlement? 5. Why d different transprtatin grups lead t the delivery split? 6. Hw can the split be affected via the cpy cntrl? 7. Hw can a delivery split per schedule line be explained fr scheduling agreements? 8. Which ptins are there t find ut the reasn fr a split? 1. Questin: Which fields lead t a delivery split? Basically, all fields which are cpied t the header f the delivery (table LIKP) via the rutines f the cpy cntrl lead t a delivery split. Furthermre, sme fields are cpied t the header by all means and are relevant fr the split there. Split fields that cannt be changed are: VSTEL KUNNR ROUTE Shipping pint Gds recipient Rute The fllwing split-relevant fields can be affected via the cpy cntrl, hwever, they shuld nt be filled differently frm the defaults since they are necessary fr the cntrl f the shipping prcess: VKORG AUTLF VSBED FKARV LIFSK STAFO Sales rganizatin Full delivery indicatr Shipping cnditin Billing type (custmer billing dcument) Delivery blck Update grup fr statistics Page 1 f 5

2 SAP Nte FAQ: Delivery split when creating STWAE Statistics currency KKBER Credit cntrl area KNKLI Accunt number f the custmer with the credit limit default GRUPP Custmer credit grup SBGRP Prcessr grup fr credit management CTLPC Credit management: Risk categry CMWAE Currency key f the credit cntrl area WAERK Currency f the sales dcument INCO1 Incterms 1 INCO2 Incterms 2 KZAZU Indicatr rder cmbinatin KDGRP Custmer grup PERFK Invicing dates (calendar identificatin) Yu must nte that, as f Release 4.0, a split des nt ccur fr sme f the fields described here if the field is filled in the very dcument delivered, hwever, if it is initial in the ther ne. In this case, n delivery split ccurs and the cntents f the nn-initial field are cpied t the header f the delivery. Fr example, this cncerns the rute. The delivery date (LFDAT) is a cmmn splitting criterin with utbund due fr prcessing with regard t stck transfer rders. Fr this, yu must take SAP Nte int accunt. 2. Questin: What is meant by delivery split accrding t the warehuse number? If the picking prcess r the putaway prcess require that nly ne warehuse number has been assigned t a delivery, yu can achieve via the delivery split accrding t warehuse number that the are created fr single warehuse. With a delivery fr single warehuse, the strage lcatins f all delivery items must refer t the same warehuse number, r they may nt belng t any warehuse number. In Custmizing (Lgistics Executin -> Shipping -> Deliveries -> Delivery Split by Warehuse Number), yu can set whether a delivery must be fr single warehuse. The respective setting per delivery type and per warehuse number is the prerequisite fr the autmatic creatin f fr single warehuse. Bth settings are necessary. 3. Questin: Why des a split ccur due t deviating partners? All partners which stand in the partner schema f the delivery and that are cpied frm the preceding dcument r that are determined frm the custmer master recrd f the gds recipient are a splitting criterin. The nly mandatry partner f the utbund delivery is the gds recipient. If, fr example, n statistical data is affected, yu can delete the sld-t party frm the partner schema fr with rder reference and it is then n splitting criterin anymre. The fllwing may lead t a split in the delivery: Page 2 f 5

3 SAP Nte FAQ: Delivery split when creating Different partner numbers fr the same partner functin. Deviating addresses f the partners even if the partner number is the same. Here, nly the address number is crucial fr the split; the address list parts are nt checked. The frwarding agent as an additinal partner in ne f the sales rders invlved. In cntrast, additinal partners with ther rles d nt lead t the split in the standard. Fr this, yu can find mre infrmatin in SAP Nte Questin: Which fields lead t the split with internal settlement? An utbund delivery is relevant fr internal settlement under the fllwing cnditins: If the cmpany cde f the sales rganizatin f the delivery deviates frm the cmpany cde f the delivering plants f the delivery items and if in additin the billing type fr internal settlement has been entered at the rder type which is the basis f the delivery. In this case, the rganizatinal data determined frm the plant master is cpied fr internal settlement t the header f the delivery and is then split-relevant: FKAIV VKOIV VTWIV SPAIV KUNIV PIOIV identificatin) Billing type fr internal settlement Sales rganizatin fr internal settlement Distributin channel fr internal settlement Divisin fr internal settlement Custmer fr internal settlement Invice date internal settlement (calendar A delivery split ccurs if different rganizatinal data has been assigned t the supplying plants relevant fr the internal settlement r if the sales rders t be delivered have different billing types fr the internal settlement. Fr this, yu must refer t nte Questin: Why d different transprtatin grups lead t the delivery split? As f Release 4.0, the transprtatin grup is cpied frm the material master f the delivered items t the header f the delivery in the SAP standard system and therefre it acts as a splitting criterin. With the mdificatin frm nte fr rders r nte fr purchase rders, yu can prevent the split; then, the transprtatin grup is nt cpied t the header f the delivery. Here, yu must bear in mind that the Page 3 f 5

4 SAP Nte FAQ: Delivery split when creating transprtatin grup is imprtant fr the rute determinatin. 6. Hw can the split be affected via the cpy cntrl? Via the cpy cntrl, the data is cpied frm the preceding dcument t the header f the delivery and therefre acts as splitting criterin. Tw rutines are relevant fr the data transfer fr utbund with rder reference in the standard: FORM rutine DATEN_KOPIEREN_001 (include FV50C001) fr the transfer f the data frm header (CVBAK) and item (CVBAP) f the sales rder. FORM rutine DATEN_KOPIEREN_002 (include FV50C002) fr the transfer f the data frm the business data f the sales rder. With all ther utbund delivery types as well as with inbund, the data transfer is carried ut via FORM rutine DATEN_KOPIEREN_301 (include FV50C301) r DATEN_KOPIEREN_201 (include FV50C201). In the table with delivery header data LIKP, there is field ZUKRL which can be filled with any values via the cpying cntrl. The cntents f this field act as splitting criteria fr the delivery creatin s that yu can use it in rder t frce a delivery split accrding t yur wn specificatins. Apart frm that, the field des nt have any business r technical imprtance and can be delivered via bth f the rutines mentined abve. Yu can find mre detailed infrmatin in nte Questin: Why des a split ccur per schedule line fr scheduling agreements? Yu can find a detailed explanatin cncerning the system behavir in nte Here, the system als ffers slutin ptins in rder t be able t prevent the delivery split by time/release date. 8. Which ptins are there t find ut the reasn fr a split? A simple ptin t subsequently find ut the reasn fr a split is that yu have reprt ZLE_ANALYZE_DELIVERY_SPLIT frm nte run fr the tw generated. The reprt returns a list f the header data deviating frm each ther and therefre indicates t a certain extent which data culd have led t a split. Anther ptin (as f Release 4.6) is the activatin f the split analysis accrding t nte This split analysis is written in the lg f cllective prcessing Page 4 f 5

5 SAP Nte FAQ: Delivery split when creating Other terms Reasn and Prerequisites Slutin. Header Data Release Status: Released fr Custmer Released n: :11:15 Master Language: German Pririty: Recmmendatins/additinal inf Categry: FAQ Primary Cmpnent: LE-SHP-DL Delivery Prcessing Secndary Cmpnents: LE-SHP-DL-LA Inbund Delivery Valid Releases Sftware Cmpnent Release Frm Release SAP_APPL 30 31I 31I SAP_APPL 40 40B 40B SAP_APPL 45 45B 45B SAP_APPL 46 46B 46B SAP_APPL 46C 46C 46C SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL T Release and Subsequent Related Ntes Number Shrt Text FAQ: ATP cmpsite nte Undesired delivery split when creating via BAPI Split analysis activatin during delivery creatin Why was there a delivery split during creatin? Several fr rush rder Page 5 f 5