High- Level Specification

Functional Overview

For the fulfilment of intercompany consignment fill-ups, the line item storage location must be determined in the fill-up (and not the subsequent delivery as per SAP standard) to ensure:

1. The stock passes through the correct storage location as defined by the finance and tax requirements - in this case, a virtual customer specific location specifically for intercompany consignment fill-ups will be used.

2. The subsequent intercompany purchase order can be correctly triggered.

Therefore this development requires:

1. The creation of a custom table in SAP where the storage location can be defined by a combination of sales org, plant, ship-to party & material.
2. When creating a line item or changing the plant in a consignment fill-up, the custom table is checked on save and the line item storage location is updated.

The set up of entries in this custom table will be the trigger for the consignment fill-up to be fulfilled using an intercompany STO. If no entries exist in this table then the consignment fill-up will be fulfilled using the standard non-intercompany process from the default plant and storage location combination.

Scope and Objectives

The scope of this development will cover all consignment fill-ups created in SAP S/4 - both China and RoW instances.

Part 1 - Custom table

• All fields to be defined are standard SAP fields as below:
  • Sales org (VKORG)
  • Plant (WERKS)
  • Ship-to party (KUNNR)
  • Material (MATNR)
  • Storage location (LGORT)

Part 2 - Storage location determination

• If sales document type (VBAK-AUART) = 'KB' or 'KBB' then each time document created, a new line is added or the plant is changed read custom table from part 1 and update sales order line item with the defined storage location (VBAP-LGORT).
• To determine the ship-to party use sales order no from VBAK-VBELN then get the ship-to party from VBPA (Partner function PARVW = 'SH')
• Save the updated changes.

Process Flow Diagram 

This system enhancement is only applicable for the highlighted L5 step below:

The following SAP applications and transaction codes are in scope for this enhancement:

SAP Fiori

• Manage Sales Orders – Version 2 (app ID - F3893)

  • Create Sales Orders

  • Change Sales Orders

SAP GUI

• Sales Orders

  • VA01 – Create Sales Order

  • VA02 – Change Sales Order 

Assumptions

This development is designed for the expected consignment fill-up types of 'KB' & 'KBB' - in the unlikely scenario that new consignment fill-up types added then these need to be added into the logic above. The only practical option is to use document type as there are no other indicators that a sales document is for consignment purposes (such as doc category). In theory the movement type associated with the schedule line type could be used - as this is unique for consignment - but this may slow down the speed of the update. 

Dependencies

Definition of the relevant storage locations and plant assignment.

Security, Integrity and Controls

An additional transaction code needs to be created to allow maintenance of the custom table for storage location determination defined above.

This table must be defined as master data in order that the specified user can update - it should be included within the Customer Representative role.

Configuration Requirements

n/a

Language Requirements

n/a

Special Requirements

n/a

Design Rationale

Functional Requirements

Part 1 - Define a custom table as below using the attributes of the standard SAP object (e.g. VKORG, WERKS etc) as specified

• Sales org (VKORG)
• Plant (WERKS)
• Ship-to party (KUNNR)
• Material (MATNR)
• Storage location (LGORT)

Part 2 - Determine Storage location at sales order item level

• If sales document type (VBAK-AUART) = 'KB' or 'KBB' then on the initial creation, if a new line item is added or if plant is changed in the line item read custom table from part 1 and update sales order line item with the defined storage location (VBAP-LGORT).
• To determine the ship-to party use sales order no from VBAK-VBELN then get the ship-to party from VBPA (Partner function PARVW = 'SH')
• Report error message if no entries found in the custom table. 
• Save the updated changes.

Rational for why standard SAP not sufficient

The process defined in part 1 and part 2 must be used as standard SAP only allows the determination of the storage location within the delivery document rather than the sales order. Therefore, if no enhancement implemented each time an intercompany consignment fill-up is created, the user would need to know that this specific ship-to / material combination should be supplied from a cross-company plant and make the necessary updates manually in the line item storage location field. Additionally, any consignment fill-ups created automatically (e.g. from EDI) would need to be manually updated.

Proposed Technology to Use

User exit - USEREXIT_SAVE_DOCUMENT_PREPARE within standard SAP S/4 program MV45AFZZ.

Data Source Considerations

n/a

Data Validation Considerations

n/a

Custom Tables

Processing Logic

Before saving the sales order:

1. Check if document type (VBAK-AUART) = 'KB' or 'KBB'
2. If true then check custom table above with parameters below to retrieve storage location (LGORT)
   1. VBAK-VKORG
   2. VBAP-WERKS
   3. Ship-to party - identify by using the sales order no from VBAK-VBELN then get the ship-to party from VBPA (Partner function PARVW = 'SH')
3. Insert storage location (LGORT) into VBAP-LGORT.

Volumetrics

Approx 600 consignment fill-ups per year across all GBUs will be intercompany consignment.

Performance Considerations

n/a

Error Handling

The custom table should validate the entries as per standard SAP object rules - e.g. a sales org entered should be a valid sales org in the system. If not, standard SAP error message 'Entry XXXX does not exist' should be displayed.

Additionally:

1. Ship-to party must be set up in sales org entered. If not then should display standard error message 'Ship-to party XXXX not set up in sales organisation XXXX' (checking master data table KNVV)
2. Material must be set up in both plant and sales org entered. If not then should display standard error message 'Material XXXX not set up in plant XXXX / sales organisation XXXX' (checking master data tables MARC & MVKE)
3. Storage location entered must be set in the plant entered. If not then should display standard error message 'Storage location XXXX does not exist in plant XXXX' (checking master data table MARD)

Testing

How to Test

Test Conditions and Expected Results for Part 1 - Custom Table

Test Conditions and Expected Results for Part 2 - Storage location definition

Test Considerations/Dependencies

Relevant intercompany storage locations must already be set up against the relevant plants.

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

Appendix

Custom Authorization Group Naming Convention

This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log