Scribd Logo
Importer

Bienvenue sur Scribd !

  • Model For Import Integration

    Transféré par

    Ravitej Vemulapalli V
    20 vues3 pages
    The document outlines a process model for importing finished goods (FG) planning between HUL and U2K2 systems. Key steps include: 1) HUL APO forecasts demand and releases to depots, which is propagated to port locations using SNP heuristics. 2) CTM runs at port locations to create purchase requisitions connected to vendor locations, which flow to HUL R3. 3) Purchase orders are created in HUL R3 and flow to HUL APO and U2K2 APO via data replication. 4) Demand is released in U2K2 APO and sales orders are created in U2K2 R3 against contracts triggered by

    Description originale:

    Titre original

    Model for Import Integration

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Formats disponibles

    DOCX, PDF, TXT ou lisez en ligne sur Scribd

    Avez-vous trouvé ce document utile ?

    Ce contenu est-il inapproprié ?

    Signaler ce document
    The document outlines a process model for importing finished goods (FG) planning between HUL and U2K2 systems. Key steps include: 1) HUL APO forecasts demand and releases to depots, which is propagated to port locations using SNP heuristics. 2) CTM runs at port locations to create purchase requisitions connected to vendor locations, which flow to HUL R3. 3) Purchase orders are created in HUL R3 and flow to HUL APO and U2K2 APO via data replication. 4) Demand is released in U2K2 APO and sales orders are created in U2K2 R3 against contracts triggered by

    Droits d'auteur :

    Attribution Non-Commercial (BY-NC)
    Téléchargez comme DOCX, PDF, TXT ou lisez en ligne sur Scribd
    Signaler comme contenu inapproprié
    20 vues3 pages

    Model For Import Integration

    Transféré par

    Ravitej Vemulapalli V
    The document outlines a process model for importing finished goods (FG) planning between HUL and U2K2 systems. Key steps include: 1) HUL APO forecasts demand and releases to depots, which is propagated to port locations using SNP heuristics. 2) CTM runs at port locations to create purchase requisitions connected to vendor locations, which flow to HUL R3. 3) Purchase orders are created in HUL R3 and flow to HUL APO and U2K2 APO via data replication. 4) Demand is released in U2K2 APO and sales orders are created in U2K2 R3 against contracts triggered by

    Droits d'auteur :

    Attribution Non-Commercial (BY-NC)
    Téléchargez comme DOCX, PDF, TXT ou lisez en ligne sur Scribd
    Signaler comme contenu inapproprié
    sur 3

    Model for integration Business case: Currently FG exports /Imports planning happens in SUMI, Centrally manual contracts/ Sales

    orders are created for the frozen period and for the rest of the weeks the forecast is loaded as independent requirement in R/3 and the planning for the subsequent lower level materials will happen. Going forward for AAC customers, SUMI tool needs to be sunset and the entire planning /Purchase / sales should happen between the U2K2 R/3/ APO & HUL Fusion R/3 /APO. For Non AAC customers still the planning will continue in SUMI.

    Process Model to be followed for Import FG planning:

    The location structure in HUL APO is as below o Depots o Super Mother Depots o Port Location o Vendor Location

    HUL APO team will forecast in DP and the same will be released as per release cycle at downstream location (depots). The demand at the depots will be propagated upto port location using SNP Heuristics in weekly bucket. PR will get created based on the master definition (procurement type F, T lane and Quota) at Destination location SNP HEURISTIC / CTM RUN
    A

    Run SNP Heuristics to propagate requirements from Depots to Port location

    Run CTM at Port location which is connected to Vendor location

    Deployable Purchase Requisition created and transferred to R/3

    In HUL APO landscape SNP PRs will not move to R/3 through CIF, to overcome this issue HUL APO runs CTM at Port location. PRs will get created on vendor as a result of CTM, and the same will be flow to HUL R/3. The business Users in HUL R/3 converts PR to PO in the frozen period. The PO will flow from HUL R/3 to HUL APO The PRs will be extracted into HUL APO BIW Data Source, which will be replicated at U2K2 APO BIW. The data transfer happens through qRFC. The product in U2K2 APO BIW data source changes based on the custom mapping. Code mapping needs to be maintained in U2K2 system for converting 8 digit U2K2 codes to 7 digit HUL codes, In case the codes are not aligned. The Demand in U2K2 APO BIW will be released to U2K2 APO SNP for planning The PO in the HUL R/3 system once released, System will trigger an IDOC Message through PI to the source of Supply (U2K2 R/3) and creates a contract.

    The lead time between customer port location & Shipment location (India port) needs to be maintained in U2K2 system. Sales order will be created in U2K2 R/3 based on the contract by the user. In U2K2 R/3 outbound delivery and Shipment will be made against the Sales Order, ASN will be generated once the actual dispatch happens. Once the shipment is confirmed from U2K2 R/3, system will trigger an ASN from source of supply (U2K2 R/3) to receiving plant (HUL R/3) through IDOC format, which creates IBD in HUL R/3. Goods Receipt happens at HUL R/3. Total lead time will be maintained on lane between port and vendor in HUL R/3

    Vous aimerez peut-être aussi