Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

TRANSACTION SINCE (S4)PACG SP06

The arrival date determination feature applies only to the service order-based integration scenario.

Because the ‘Arrvival date’ depends on multiple factors, in order to get the most exact date, the /PACG/ECM_RMAT_ARRIV program should be scheduled as a background periodical job. The program reads all subsequent documents and updates ARRIVAL dates accordingly.

The Arrival Date is also determined automatically right after reserved material creation however the logic behind its determination is very simplified - requirement date for component is used. Proper, scenario-dependent dates are determined after executing program https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1722679297, which should be scheduled as a regular job.

FSM Connector is capable of calculating an arrival date for reserved materials and then sending an update to the FSM. This transaction can take the following parameters:

  • Order (service orders number) - range of service orders' number for which reservations should be checked

  • Material - range of materials included in the reservations

  • Created on - range of reservation creation dates (the dates when reservation was created and not the orders they belong to)

The ‘Arrival date’ itself depends on the type of the process:

  • MM Process – Purchase requisition & Purchase Order
    First date is picked from purchase requisition and it is requested delivery date.

When purchase order is created then confirmation lines are considered. If there are no confirmation lines ‘delivery schedule’ are checked and ‘delivery date’ is taken.

  • SD Process – Consignation fill-up
    Schedule lines are considered and ‘delivery date’ is picked up. In case of multiple schedule lines, the latest (worst) delivery date is considered

If a delivery document exists and its Planned Goods Issue date is lower or equal than the delivery date from schedule lines, this date will be taken instead.

image-20240917-133524.png

 Click to see an example

MATERIAL 1 has quantity 10: 

 ARRIVAL date comes from schedule lines in consignment order.

 

In the order, there are 3 schedule lines for this material:

  • Quantity 5 is confirmed on 01.03.2023

  • Quantity 3 is confirmed on 02.03.2023

  • Quantity 2 is confirmed on 03.03,2023 

 As ARRIVAL date, ‘the latest’ date from those schedule lines will be taken, because full quantity 10 PC will be available on 03.03.2023 (partial quantity is available before, but full quantity on 03.03.2023). 

Arrival date used to be displayed only for reserved materials before goods issue for delivery. However, the time between goods movement and arrival to the customer can take longer. (S4)PACG SP13 Now, the delivery date is also determined for reserved materials after goods movement for delivery. At first, the arrival date is copied from the related unshipped ('R') reserved material entry. Then it can be recalculated with program https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1722679297 if schedule lines change.

  • Reservation on ‘VAN stock’
    Requested delivery date is retrieved

  • No labels