Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
OIG (Package) TD Transport and Distribution
IMG Activity
| ID | SIMG_OIG_TD_001 | Define Goods Issue at Loading and Proof of Delivery |
| Transaction Code | S_SO7_28000003 | (empty) |
| Created on | 20030407 | |
| Customizing Attributes | SIMG_OIG_TD_001 | Define Goods Issue at Loading and Proof of Delivery |
| Customizing Activity | SIMG_OIG_TD_001 | Define Goods Issue at Loading and Proof of Delivery |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_OIG_TD_001 |
Use
In this IMG activity, you can define how the system is to process goods issues during the loading and delivery confirmation processes in the Transportation and Distribution (TD) component. You enter the Incoterms and define if deliveries are relevant for goods issue at loading.
You can select the following processing options for goods issues (GI) of the relevant deliveries (not stock transfers) during TD loading and during delivery confirmation:
- GI at loading, proof of delivery at delivery confirmation
The final discharge quantity is known and the system can record this at delivery confirmation. The system automatically calculates the difference between the load and discharge quantities before triggering the proof of delivery functions. The status and corresponding fields (quantity and dates) in the delivery are then updated. The final (or differential) invoice can now be created.
- GI at loading, quantity at delivery confirmation for statistical purposes and freight
The discharge quantity is taken for statistical purposes. This means the final delivered quantity is updated only in the shipment database, not in the delivery document. The invoice is based on the loaded quantity.
- GI at loading, no delivery confirmation
A delivery confirmation is not needed. The shipment is completed (fully confirmed) only at loading confirmation. The Balance Vehicle screen does not post a gain or loss as the discharge quantity is set as the loaded quantity. The invoice is based on the loaded quantity.
In first and second cases, the Balance Vehicle screen uses the discharge quantities to calculate a gain or loss but no material document is generated to post the gain or loss.
Exception:
If there is a goods issue at loading, and quantity left on vehicle or returns quantity at delivery confirmation, the specified quantity in the delivery confirmation results in a corresponding gain posting to MM.
Requirements
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_OIG_TD_001 | 0 | I270009310 | Transportation and Distribution |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TINC_OIG | V - View | SM30 |
History
| Last changed by/on | SAP | 20030407 |
| SAP Release Created in | 472 |
