Posting of Subsequent Costs

You can use this function to post and repost costs that occurred after you created an invoice. In several cases not all the costs are known at the moment when the customer would like to get back the repaired car or ordered vehicle or part. You have to create the invoice although not all items are processed. A further situation is if you have to correct costs after you created the invoice.
After you create an invoice, you can post and repost this subsequent costs from the header internal order to the bill-to party internal order for the following two processes:

• Change of time sheet data after invoice creation
• Price difference between purchase requisition and incoming invoice (for external services with purchase order)

Prerequisites

For the process change of time sheet data after invoice creation, you have implemented user exits for the Cross-Application Time Sheet. You have created an implementation for the enhancement CATS0006, and have changed the coding of the enhancement CATS0002, to ensure that the VSS Order is updated accordingly if subsequent costs were posted for it.

• CATS0002: The method /DBE/CL_TM_VSSDATA_EXAMPLE->SET_SUBSEQ_COSTS contains the logic to set the flag in the VSS order, that subsequent costs occurred. Corresponding coding must be added to the include ZXCATU02.
• CATS0006: To save the updated VSS order, add coding to the include ZXCATU05, such as the method /DBE/CL_TM_VSSDATA_EXAMPLE->SAVE_ORDER.

Features

The figure below illustrates the time frame from posting of subsequent costs and is followed by an explanation:

Posting and Reposting Subsequent Costs

You can post and repost subsequent costs within the time frame from the first invoice until you close the VSS order for subsequent costs. You can choose the following possibilities to repost costs:

• Calling the event Reposting Subsequent Costs (REPOST_SUB_COSTS) in the VSS order
• Using the report VSS Subsequent Costs Reposting (/DBE/SUBSEQ_COSTS) in transaction SE38 for mass processing of corresponding VSS orders

If you post subsequent costs, the system sets the order status REPOST_LINE_ITEM of the relevant split items and split header to Partially Processed.
If you repost subsequent costs, the system sets the order status REPOST_LINE_ITEM of the relevant split items and split header to Completely Processed.

Close Order for Subsequent Costs

You can close the VSS order for subsequent costs in one of the following ways:

• Calling the event Close Order for Subsequent Costs (SUB_SEQ_CLOSE) in the VSS order
• Using the report VSS Closing Order for Subsequent Costs Processing (/DBE/SUBSEQ_CLOSE) in transaction SE38 for mass processing of corresponding VSS orders

The system sets the status of the first level internal order to Complete.

Open Order for Subsequent Costs

To reopen the VSS order for subsequent costs, you call the event Opens Order for Subseqent Costs (RESET_SUB_CLOSE). The system resets the status of the first level internal order.

Final Close of Order

You close the VSS order finally for subsequent costs in one of the following ways:

• Calling event Final Close of Order (ORD_FINAL_CLOSE)
• Using the report VSS Final Close of Orders (/DBE/ORD_FINAL_CLOSE) in transaction SE38 for mass processing of corresponding VSS orders

After the final close of the VSS order, you cannot reopen the VSS order for subsequent costs. The system flags the first level internal order for deletion.