In the “old” command (ME21), the system only checks availability when you leave the planning screen. A STSA is a document that authorizes several transfer releases against it, such as . B a contract. This type of agreement is useful for frequent relocation requests with a supplier/company. After implementation, the system can establish classifications against the agreement requiring minimal human intervention. If the system accepts a delivery, i.e. if the quantity at the output of the product is sufficient according to the subcontracting tolerance, the post-delivery license plate is automatically set in order. Is there a possibility that this STSA could work for storage reservations on sites such as production lines and be linked to the release of the production order??? If you have selected in the customizing the outsourcing tolerance for relocations, the delivery is considered finished for the contract. The remaining quantity is no longer considered a need in the delivery facility. In this step, you enter the shipping-specific data for inter-factory relocation processing.
B for example the customer number of the delivery plant. Can someone help me differentiate transfer orders (STO) and transfer delivery plan (STSA) from SAP`s perspective? Test rule for transfer plans. A standard STO is a unique document for a single transaction, just like a single order to a supplier. Whenever it is necessary to transfer stocks; a new STO must be created. 2. Enter the necessary data. The lu chord type is defined in the standard system. The item category must be U. Enter the end date. Testing method for proofs of re-adjustment: a check on the availability of relocation certificates during rescheduling is carried out in accordance with the test carried out during the manual preparation of a proof. However, if the required quantity is not available for a calendar on a given date and is not ready until later, new classifications will be established for relocation and delivery plans containing the relevant data. In this case, new positions are created for conversion requirements.
The total ranking amounts for a processed calendar position correspond to the ranking volume of the initial calendar line. First example: Use a transfer command post with aschedule line:a) item status before reprogramming run:Del.