Consignment 
Use
General characteristics:
· Uniformly mappable independent of the system distribution
· Profit Center Accounting can be mapped using changes in controlling areas.
· All relevant information (key fields) about the business partner are transferred during system transitions: For example, partner information, material information, dangerous goods information, profit center information, controlling area, plant, company code, (partner FI BA).
· Repeated transactions do not result in repeated price negotiations.
· Repeated processing is supported by outline agreements and scheduling agreements.
· The change in business area must be taken into account, depending whether the supplying business area is different from the selling profit center. This case is basically the same for all scenarios.
Prerequisites
SAP only supports cross-company-code consignment processing.
· The number of process variants is a result of the combination of system landscape and organizational units:
¡ One or more ERP systems
¡ Cross-company code
¡ Within a profit center or cross-profit-center
¡ With or without joint APO
For more prerequisites, see Cross-System Stock Transfer (Intra-Company-Code), section Prerequisites.
Process Flow
You can use this function to process cross-company-code deliveries of consignment material in two steps, both within a single system (one system case) and between two systems (two system case). In a two-step process, you withdraw the material from a stock that is not assigned to a special stock. This means that you have to enter the goods receipt in a separate step.
The goods issue posting on the issuing side represents a transfer posting from your own unrestricted-use stock, into the customer consignment stock at the customer. On the receiving side, the system posts a GR posting for this consignment stock, with movement type 101K. This means that the consignment stock on the receiving side is managed as vendor consignment stock. In the two system case, the systems communicate via IDoc. There is no link between the customer consignment stock and the vendor consignment stock. After the goods receipt is posted at the receiving side, this consignment stock appears no different than the consignment stock procured in a different way.
The system does not support consignment returns posting.
One-System Case
In the one system case, the transfer posting on the receiving side is made from the unrestricted-use stock into the customer consignment stock, using movement type 635 (reversal movement type 636). The following goods receipt posting cannot be made with reference to the outbound delivery. For this reason, the GR posting does not update the delivery. The system does not support working with serial numbers.
Two-System Case
In the two-system case, the movement types on the issuing side are 6W5 and 6W6, instead of 635 and 636. On the receiving side, the material documents are posted with movement types 6K5 and 6K6 (similar to 6W5/6W6). The only purpose of this posting is to update the PO history in the receiving system.
In contrast to the one system case, serial number processing is supported, because serial numbers are managed in different systems at goods issue and goods receipt.
The document flow update for the delivery is not supported. You must post the goods receipt with reference to the purchase order.
Processes Supported
The following processes are generally supported by SAP:
...
Consignment Within an ERP System with SAP APO
Consignment Between Two ERP Scenarios and SAP APO
This scenario is realized with the new function for unchecked deliveries.
Effects on SAP Business Objects
You can see the affected SAP processes in the process diagrams.
Structure of the Complete Concept in Subprocesses
· Linking APO System and ERP System
· Converting Unchecked Delivery into Delivery
· Goods Issue for the Delivery
· Goods Receipt for Purchase Order