Archives par mot-clé : CIF

Transfert de ressources ECC->APO

Publié le par

Les ressources ne sont pas une donnée vraiment dynamique donc il n’est pas nécessaire de les inclure dans un modèle d’intégration quotidien.

Le plus simple est de les intégrer manuellement au besoin.

Pour que les gammes soient correctement intégrées, il faut que les ressources existent dans un modèle d’intégration actif. Cela n’est pas forcément possible si les ressources ont été modifées dans leurs dimensions dans APO. L’astuce est d’intégrer les ressources dans APO quitte à passer par des modèles séparés, puis de faire un modèle global et de l’activer en dialogue (pas en arrière plan). L’activation ne vas pas marcher et une queue inbound apo en transfert initial va se créer. La supprimer. Le modèle est activé, les ressources sont dans APO, tout est prêt pour la suite.

Publié dans APO | Marqué avec ,

Tips and techniques to smoothly and seamlessly transfer data between SAP APO and SAP ERP, leveraging the core interface (CIF)

Publié le par

Master Data Exits — SAP APO

Business Add-Ins (BAdIs) and customer exits

  • Exist for each publication type
  • Can be used to interrupt the program flow during the sending phase of direct and periodic sending

Master data exits

  • Inbound processing: Location — APOCF001 EXIT_/SAPAPO/SAPLCIF_LOC_001
  • Inbound processing: Resource — APOCF008  EXIT_/SAPAPO/SAPLCIF_RES_001
  • Inbound processing: Products — APOCF005   EXIT_/SAPAPO/SAPLCIF_PROD_001
  • Inbound processing: PPM — APOCF012   EXIT_/SAPAPO/SAPLCIF_PPM_001
  • BAdI: PPDS PDS — /SAPAPO/CURTO_CREATE
  • BAdI: SNP PDS — /SAPAPO/CURTO_SNP
  • Inbound processing: Source of supply — APOCF032EXIT_/SAPAPO/SAPLCIF_TPSRC_001

Transaction Data Exits — SAP APO

  • Inbound processing: Stock — APOCF011 EXIT_/SAPAPO/SAPLCIF_STOCK_001
  • Inbound processing: Production orders and planned orders — APOCF004 EXIT_/SAPAPO/SAPLCIF_ORD_001
  • Outbound processing: Production orders and planned orders — APOCF013 EXIT_/SAPAPO/SAPLCIF_ORD_002 (before send user exit)
  • Inbound processing: Purchase order documents — APOCF006 EXIT_/SAPAPO/SAPLCIF_PU_001
  • Inbound processing: Sales and distribution document — APOCF010 EXIT_/SAPAPO/SAPLCIF_SLS_001

SAP R/3 Exits

Customer exits in SAP R/3 for the publication types:

  • CIFORD03: Change Order Data
    • To change orders that are transferred from SAP APO to SAP R/3 in R/3 inbound queue
  • CIFORD01: Change Object Type and Order Data
    • To change order data that is transferred from SAP APO to SAP R/3 and is already in SAP R/3 format in R/3 inbound queue
  • PPAPO002: Influence Order Data after the Transfer from SAP APO
    • To influence the data that was transferred from SAP APO to SAP R/3 for a manufacturing order before it is transferred to the SAP R/3 manufacturing order
  • PPAPO008: Override Order Type for Planned Order Conversi on
    • To manually influence the order type of a manufacturing order generated by conversion from SAP APO (customer exit EXIT_SAPLCOXT_002)
  • PPAPO004: Re-Explode BOMs for Planned Order Conversion
    • To force the re-explosion of a BOM (customer exit EXIT_SAPLCOXT_001)
  • PPAPO009: Add Components and Items
    • To run own checks when components are added to a manufacturing order from SAP APO
  • PPAPO007: Override Checkbox Fields for Manufacturing Orders, SAP APO ® SAP R/3
    • To override checkbox fields for manufacturing orders on transfer from SAP APO to SAP R/3
  • Material master — CIFMAT01  EXIT_SAPLCMAT_001
    • To add new fields in the material master that are in SAP APO but not in SAP R/3 (for SAP R/3 to be the material master system of record, this user exit is necessary to add the new fields)
  • PDS transfer — CUSLNTRTO_ADDIN_SAP
    • To influence values and change fields on the PDS that are transferred to SAP APO from SAP R/3
  • CIFPUR01 (enhancement for the transmission of customer-specific purchase order fields)
    • To change purchasing data from purchase requisitions, POs, scheduling agreement schedule lines (OLTP scheduling agreement), and confirmations/shipping notifications (for SAP APO and OLTP scheduling agreements)
  • CIFPUR02 (enhancement PO interface — inbound)
    • To change PO data from SAP APO before a purchase req, scheduling agreement schedule line, or a PO is created in the OLTP system

Additional Exits

Customer exits for orders and manufacturing orders in SAP APO

  • APOCF020 — User-specific fields in the order interface (after posting in SAP liveCache or to the database)
  • APOCFPIP — Publication of in-house production orders (planned orders, manufacturing orders)

BAdIs

  • /SAPAPO/CL_EX_CIF_IP — Comparison of APO data and CIF data
    • To control if and when the activity dates planned in SAP APO should be rescheduled, or if a change to the order quantity in SAP R/3 leads to a proportional change to receipt and requirement quantities