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

Specify the configuration requirements for this object. Like in case of substitution/ routine specify the configuration needed

Language Requirements

Specify the language requirements for this object. Specify the required language and type of translation, like labels, data.

Special Requirements

Specify any special requirements or considerations that may impact the enhancement based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China

If the enhancement interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.

Design Rationale

Functional Requirements

Detail the functional requirements that are desired to be achieved by the Enhancement compared to current functionality

Proposed Technology to Use

Typically, an enhancement will be based on an existing SAP BADI / user exit. If this is the case, please provide the proposed details of the BADI / user exit.

Data Source Considerations

Include an overview of the source. Can be deleted if not needed.

Data Validation Considerations

Include an overview of the data validation requirement. Can be deleted if not needed.

Custom Tables

If any custom configuration tables are required, which will be read by the enhancement logic, then specify them here. Can be deleted if not needed.

Master Data

<Title Custom Table 1>

<Include an overview of the table and what it’s used for>

Configuration Table

Title Configuration Table 1

Include an overview of the table and what it’s used for

Selection Screen Enhancement

This section will give the details on the selection screen parameters, parameter type and whether it’s obligatory or not. This section can be used to define the Import Export parameters for Function Module or User Exit or Screens. Can be deleted if not needed.

Processing Logic

This section defines the detailed step-by-step logic implemented within the BAdI/User Exit to process the data received from the standard SAP program and database retrieval. It explains the operations performed on the data, the expected outcomes in different scenarios and how the system should behave in response to specific conditions.

Volumetrics

Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)

Performance Considerations

Specify if there are any specific performance factors that need to be taken into consideration during development i.e. enhancement must be able to be executed by 10 users at the same time, etc.

Error Handling

Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.

Test Conditions and Expected Results

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

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