In past post, http://saprainbow.com/sap-pi-adapter/simple-any-file-to-file-scenario-in-id-only-without-esr-objects/ will copy any file to file with dummy interface using integration directory only. In this post, will achieve the thing but in SAP PO AEX, using NWDS, iFlow and ICO. Objective: Create a scenario where file
SAP PO AEX Java Only Integration Flow (iFlow) and Integrated Configuration
Integrated Configuration The main different we can see from Integration Directory is, there no longer have those old faithful classic 4 objects (sender agreement, receiver determination, interface determination and receiver agreement). Instead, replaced with Integrated Configuration (also known as ICO).
NWDS – Initial Setup to Make It Run
Below are list of steps i had done to make NWDS run at my windows 2008 server PI AEX: 1. Install JAVA JDK with 32-bits version. I used version “jdk1.6.0_45”. Only 32-bits JAVA version supported. 2. Install SAP NWDS. 3.
EDIFACT DESADV and X12 856 from IDOC DESADV Basic Type DELVRY03
DESADV mean Dispatch Advice. It also known as Advanced Shipment Notice (ASN). Below show some common fields required to map from DESADV IDOC to both EDIFACT DESADV and X12 856 message type.
EDIFACT DELFOR and X12 830 to IDOC DELINS Basic Type DELFOR02
DELFOR and 830 message type is used for SAP SD schedule agreement. This post attempt to show some common fields required to map DELINS IDOC, for both EDIFACT DELFOR and X12 830 message type.
EDIFACT ORDERS and X12 850 to IDOC ORDERS Basic Type ORDERS05
Below show some common fields required to map ORDERS IDOC, for both EDIFACT ORDERS and X12 850 message type. Example EDIFACT ORDERS UNA:+.? ‘ UNB+UNOA:1+<Sender ID>+<ReceiverID>+<YYMMDD>:<HHMM>+<ICN#>++ORDERS’ UNH+1+ORDERS:D:97A:UN:EDPO04′ BGM+220+<Header PO Number>+9′ DTM+137:<Header PO Date>:102′ NAD+BY+<Customer Name/Code>::91′ NAD+SE+<Vendor Name/Code>::92′ NAD+ST+<Ship-to location>::92′ CUX+2:<Currency>:9′
UDFNodePool – Difference and Similarity between useOneContextAsMany and createMultipleContextCopies
useOneContextAsMany = Repeat contextValues at first input separated with context change, as many time as context values count at second input. createMultipleContextCopies =Repeat contextValues at first input separated with context change, as many time as numeric value at second input.
ccBPM – Merge Two Files into One File using Fork, Correlation and Transformation
This is an example to merge 2 files into 1 file using SAP PI ccBPM. Some points to considers: The contents from 2 files will be merged into 1 file, based on same ID. File part A might be available
SD Customer Master Record
Customer Master Record Customer master record consist of 3 views: 1) General data 2) Company code data 3) Sales area data Each customer partner number must have account group. Account group used to group customer partner number that have same
SD Sales Document Types + Item Categories + Schedule Line Categories
General Sales document header controlled by sales document type. Sales document item controlled by sales item category. Sales document schedule line controlled by schedule line category. Sales document types Sales document type : Document category : B=Quotation C=Sales order Sales