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 saving a consignment fill-up, the custom table is checked and the line item storage location is updated.

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 or 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:

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.

This table must be defined as master data in order that the specified user can update.

The authorization to maintain these 2 fields should be included in the Customer Representative Role as part of the Manage Sales Orders v2  - F3893, VA01 Create Sales order, VA02 Change Sales order, VA03 Display Sales order.

Add transaction code and auth role for the maintenance of the DPAS table
Maintenance Transaction
The Z-table shall be maintained via a custom transaction code, with appropriate authorization checks to restrict access and editing rights

Configuration Requirements

Language Requirements

Special Requirements

Design Rationale

Functional Requirements

Proposed Technology to Use

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

Volumetrics

Performance Considerations

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

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