High- Level Specification

Functional Overview

For the fulfilment of intercompany consignment fill-ups, the line item storage location and supplying plant 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 & supplying plant can be defined by a combination of sales org, distribution channel, 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 PO. 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.

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

  • VA02 – Change Sales Order 

Assumptions

This development is designed for the expected consignment fill-up type of 'KB'. The consignment fill-up type 'KBB' should not be included here as the process may not be compliant in Brazil.

In the unlikely scenario that new consignment fill-up types added then these need to be added into the logic above.

This development is only intended for use within a single instance - either RoW or China. This will not apply for multi-instance solution - the expectation is that this process will be manual between Row <> China.

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

Should follow the standard authorisation requirements of the sales order

Configuration Requirements

n/a

Language Requirements

No Specific language requirement - the solution should support the SYWAY language approach.

Special Requirements

n/a

Design Rationale

Functional Requirements

Determine Storage location at sales order item level

• If sales document type (VBAK-AUART) = 'KB' 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).
• Determine the storage location VBAP-LGORT by using:
  • Sales org (VBAK-VKORG)
  • Distribution channel (VTWEG)
  • Plant (VBAP-WERKS)
  • Ship-to party (VBAP-KUNWE_ANA)
  • Material (VBAP-MATNR)
• Report error message if no entries found in the custom table. 
• Save the updated changes.

Rational for why standard SAP not sufficient

This enhancement is required because 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

Tech team to confirm - fall back plan  is 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

Required custom application table entries below using the attributes of the standard SAP object (e.g. VKORG, WERKS etc) as specified. These entries are maintained in FS ERP-1371 within the CSR business role.

Processing Logic

Before saving the sales order:

1. Check if document type (VBAK-AUART) = 'KB'
2. If true then check custom table above with parameters below to retrieve storage location (LGORT)
   1. VBAK-VKORG
   2. VBAK-VTWEG
   3. VBAP-WERKS
   4. VBAP-KUNWE_ANA
   5. VBAP-MATNR
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

Testing

How to Test

For the required business function, this test must be run in 2 x parts:

 - Part 1 for the master data customer table defined in ERP-1371

 - Part 2 for the functional requirement in the intercompany consignment fill-up as specified in this document.

Test Conditions and Expected Results - 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

Change log