Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Symptom

You observe

  • 06 855 "Not possible to determine shipping point for item &1"
    (see only shipping point problem from the below list)

or

  • 06 280 "Not possible to determine shipping data for material &"

error message at Stock Transfer Order (STO) creation in any transaction in SAP ERP system. 

Also the shipping tab might not appear at all or with empty fields.

Follow below points to identify the cause and to make sure that all the necessary settings are correctly maintained:

  • Basics:
  1. Make sure according to note 1803189, that you use non-outdated transaction(s)
  2. Deactivate active enhancements which may influence the scenario:
    ME_PROCESS_PO_CUST
    MD_EXT_SUP (BAdI for Determining the Issuing Storage Location)
  3. Please also make sure that no custom Z program, or standard program-modification effect's standard program logic
  4. Based on your scenario go to the corresponding point:
    1. Stock Transfer between Plants (Stock Transfer Between Storage Locations NOT activated) -> Go to Point 1
    2. Stock Transfer between Storage locations (Stock Transfer Between Storage Locations IS activated) -> Go to Point 2
    3. STO within plants between storage locations (optional) -> Go to Point 3

Please note that the below listed problems do not include system errors, in case you observe incorrect system behavior (such as bug, unexplainable behavior, dumps, etc.) another possible source of the problem could be a missing correction note from the system. Please look for correction notes with the release level of your ERP System. You might use Automated Note Search Tool for this (see Note 1818192 for more details) purpose.

 

  1 - Stock Transfer between Plants (Stock Transfer Between Storage Locations NOT activated)
if you have activated the Stock Transfer Between Storage Locations then go to Point 2

Make sure that:

  • the STO item and it's material are not deleted
  • the "delivery completed" indicator (ELIKZ) is not ticked
  • the finally delivered (EGLKZ) or the blocked indicator are not ticked
  • there's an existing customer assigned to the receiver plant (table T001W). If a deleted customer is assigned to it, error message 06 849 is raised:
    Customizing path: ta. OLME: -> Purchase Order -> Set Up Stock Transport Order -> Define Shipping Data for Plants
    This assigned customer master record must be created for the organizational units of the supplying plant.
    For the intra-company-code stock transport, it is sufficient to create the customer master record as a goods recipient (VD01).
    For the cross-company-code stock transport with shipping and billing documents, a complete customer master record is required (XD01).
  • customer master is correctly maintained regarding the following parameters:
    client / shipping condition / loading group /plant/storage location/shipping point (customer master table: KNVV -> field: MANDT / VSBED / LADGR / WERKS / LGORT / VSTEL)
  • a delivery type is assigned to the purchase order document type/supplying plant combination:
    OLME: Purchase Order -> Set Up Stock Transport Order -> Assign Delivery Type and Checking Rule
    intra-company-code: NL (Replenishment delivery) (without a billing document)
    cross-company-code: NLCC (Replenishment delivery cross company) (with a billing document)
  • sales and distribution (SD) organization data maintained in supplying plant:
    OLME: -> Purchase order -> Set up Stock Transport Order -> Define Shipping Data for Plants
  • For the material the sales organization data for the sales organization/distribution is created channel of the supplying plant, and you must maintain the sales view (general plant data) for the supplying plant.
  • a shipping point is entered for the combination of shipping condition (customer master) - loading group (material master) - supplying plant:
    SPRO: Logistics Execution-> Shipping-> Basic Shipping Functions-> Shipping Point and Goods Receiving Point Determination->Assign Shipping Points
    (from 06 288 error’s long text the loading group the supplying plant is quickly visible - table TVSTZ)
  • sales area is maintained correctly according to Note 169586 - Sales area determination in stock transfer order (in case of Retail see Notes: 170075, 170082, 303957)
  • a default document type is maintained for STO:
    Transaction OLME/purchasing/purchase order/set up stock transport order/Assign Document Type, One-Step Procedure, Under delivery Tolerance. In this step, you define which document type is to be used for a certain combination of supplying plant and receiving plant.If the supplying and receiving plants belong to the same company code, choose the document type 'UB' or a comparable document type of your own. A physical stock transfer is then carried out without a billing document. Ensure that 'T' (for transport) (BSAKZ indicator) is entered in the 'Control' field for the relevant document type in Customizing for Purchasing under<Purchasing Object> -> Define Document Types.
    Depending on the supplying and issuing plants, you can also specify whether or not the stock transfer is to be executed according to the one-step procedure. With the one-step-procedure, the goods receipt in the receiving plant is posted at the same time as the goods issue in the issuing plant.
  • combination of partner and account group maintained in TPAKD table:
    SPRO -> Logistics Execution -> Shipping -> Basic Shipping Functions -> Partners -> Account Groups - Function Assignment -> Account Groups - Function Assignment

 

1.1 - Additional information for cross-company (intercompany) business process:
Besides the above from point 1, the cross-company STO process has the following prerequisites :

  • You must enter a vendor master record for the corresponding purchasing organization of the receiving plant.  The assignment is executed in the vendor master record from the purchasing organization screen using "Extras --> Additional Purchasing Data".
  • For cross-company code events, supplying plant and receiving plant are in different company codes, you can use both a document type with BSAKZ = 'T' and also BSAKZ = ' '. Control indicator BSAKZ defines the posting logic in inventory management (one-step or two-step).

 

2 - Stock Transfer Between Storage Locations activated by customizing path: OLME: -> Purchase order -> Set up Stock Transport Order -> Set Up Stock Transfer Between Storage Locations -> Activate Stock Transfer Between Storage Locations

Make sure that:

  • the STO item and its material are not deleted (LOEKZ)
  • the "delivery completed" indicator (ELIKZ) is not set
  • finally delivered (EGLKZ) or the blocked indicator are not set
  • a customer is assigned to the receiver storage location. In this case customer assigning to receiver plant is only optional (T001L):
    OLME: -> Purchase order -> Set up Stock Transport Order -> Set Up Stock Transfer Between Storage Locations -> Define Shipping Data for Stock Transfers Between Storage Locations
    This assigned customer master record must be created for the organizational units of the supplying plant.
    For the intra-company-code stock transport, it is sufficient to create the customer master record   as a goods recipient (VD01).
    For the cross-company-code stock transport with shipping and billing documents, a complete customer master record is required (XD01).
  • Customer master is correctly maintained regarding the following parameters:
    client / shipping condition / loading group /plant/storage location/shipping point (customer master table: KNVV -> field: MANDT VSBED LADGR  WERKS  LGORT  VSTEL)
  • an issuing storage location is entered in the STO document
    The issuing storage location field is not populated automatically in standard system, please be aware that if you use for example ME_PROCESS_PO_CUST BAdi to populate this field in ME21n, BAdi's are not called in not-enjoy transactions like ME31L, ME31K, ME41, etc.
  • a delivery type is assigned to the purchase order document type/supplying plant combination:
    OLME: Purchase Order -> Set Up Stock Transport Order -> Set Up Stock Transfer Between Storage Locations -> Assign Delivery Type and Checking Rule According to Storage Location
    intra-company-code: NL (Replenishment delivery) (without a billing document)
    cross-company-code: NLCC (Replenishment delivery cross company) (with a billing document)
  • sales and distribution (SD) organizational maintained in supplying storage location
    OLME: -> Purchase order -> Set up Stock Transport Order -> Set Up Stock Transfer Between Storage Locations -> Define Shipping Data for Stock Transfers Between Storage Locations
  • the material must have the sales organization data for the sales organization/distribution channel of the supplying storage location, and you must maintain the sales view (general plant data) for the supplying plant.
  • a shipping point is entered for the combination of shipping condition (customer master) - loading group (material master) - supplying storage loc:
    SPRO: Logistics Execution-> Shipping-> Basic Shipping Functions-> Shipping Point and Goods Receiving Point Determination->Set Up Storage-Location-Dependent Shipping Point Determination->Assign Shipping Points According to Storage Location (tvstz_storloc table)
  • sales area is maintained correctly according to Note 169586 - Sales area determination in stock transfer order
  • a default document type is maintained for STO:
    Transaction OLME/purchasing/purchase order/set up stock transport order/Assign Document Type, One-Step Procedure, Under delivery Tolerance.
  • In this step, you define which document type is to be used for a certain combination of supplying plant and receiving plant.
  • If the supplying and receiving plants belong to the same company code, choose the document type 'UB' or a comparable document type of your own. A physical stock transfer is then carried out without a billing document. Ensure that 'T' (for transport) (BSAKZ indicator) is entered in the 'Control' field for
  • the relevant document type in Customizing for Purchasing under Define Document Types.
    Depending on the supplying and issuing plants, you can also specify whether or not the stock transfer is to be executed according to the one-step procedure. With the one-step-procedure, the goods receipt in the receiving plant is posted at the same time as the goods issue in the issuing plant.
  • combination of partner and account group maintained in TPAKD table:
    SPRO -> Logistics Execution -> Shipping -> Basic Shipping Functions -> Partners -> Account Groups - Function Assignment -> Account Groups - Function Assignment

2.1 - Additional information for cross-company (intercompany) business process:

Beside the above from point 2., the cross-company STO process has the following prerequisites :

  • You must enter a vendor master record for the corresponding purchasing organization of the receiving plant.  The assignment is executed in the vendor master record from the purchasing organization screen using "Extras --> Additional Purchasing Data".
  • For cross-company code events, supplying plant and receiving plant are in different company codes, you can use both a document type with BSAKZ = 'T' and also BSAKZ = ' '. Control indicator BSAKZ defines the posting logic in inventory management. (one-step or two-step)

 

3 - STO within plants between storage locations (optional)

There is no specific STO setting for this scenario, Inventory Management movement types 311 and 313 / 315 (in transit) are offered for this purpose or you could activate "Stock Transfer Between Storage Locations" process (Go to Point 2).

 

4 - Additional info

  • Valuation type can be entered at the time of Goods Issue posting after note 1677707 is implemented, if this note not implemented yet the logic written in Note 66953 is valid.
  • Modification Note 72735 makes it possible to determine the ship-to-party via the receiving storage location, but this note does not change the standard logic of the route determination in the PO.