Implementing an EDI scenario with XI

Hi,
I need to implement an EDI scenario with a non SAP system. I would like to know what are the "components" that I should have in order to acomplish the task ?
(how is it different from an ALE scenario)
I'm new to EDI ! (so take is slow...)
Thanks, Nir.

Similar Messages

Procedures for implementing a snapshot scenario with custom DataSources

Hi Gurus,
I have checked the How To paper ([How to Handle Inventory Management Scenarios in BW (NW2004)|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]). However, only SAP standard BW objects are mentioned in the paper e.g. InfoCube (0IC_C03), Material Stock InfoSource (2LIS_03_BX), Material movements IS (2LIS_03_BF) and Revaluations IS (0LIS_03_UM).
On the contrary, I need to handle custom DataSources for the Snapshot scenario. Are there any differences in the implementation methodology? Which additional aspects should I take into consideration? For example, the load sequence, delta type, etc.
Could you please list out the step-by-step procedures for such an implementation?
Thanks in advance!
Regards,
Meng

Hi Meng,
You can approach this in two ways.
1) If the volume of data is not much, you can derive the balance at query level, as follows.
User enters the date, based on this restrict your key figure to display all values less than this date.
2) If the volume of data is high, then you will have issues with performance if you are calculating the balance in the front end. In this case, you can model this with 'Non cumulative' key figure. Again there are 2 ways of approaching this back end solution based on the volume of data. ( Say in one case you have 2 years of history in your DSO and in the second case, you have 5 years of history ).
A) For example, If there are only 2 years of history
Create a non cumulative Key figure 'ZBALANCE' with inflow and outflow, in a cube.
Map this to your credit and debit as + and - respectively and map the calender day to posting date.
Just initialise the dataload with data transfer and start loading the delta as normal.
You will be able to see the balances for each and every calday in your reporting.
This approach is straight forward and simple.
Compress the cube for getting the better performance.
B) If there are 5 years of history and you are not interested in loading all the 5 years data in getting the balance
Here you want to have the initial balance, continue delta and would like to load 2 years of history.
The cube and non cumulative KF are created as mentioned above.
For generating initial balance, you have to create another DSO without calander day and ZBalance mapped to credits and debits in additive mode. Load your DSO data into this new DSO to generate initial balance. This balance will be loaded to your cube as initial balance. ( Like 2LIS_03_BX ).
You have to compress this request with marker update ( Must ).
Load your historical data for 2 years from the original DSO. Compress without marker update ( Must ).
initialise without data transfer from DSO to cube and load deltas normally.
Compress the delta requests normally for performance reasons.
Please read the 'Inventory document' in detail.
Please let me know, if any of the information is still not clear.
Thanks,
Krishnan

Problem in simple filetofile scenario with BPM

Hi
I am a starter to XI. I am implementing simple file2file scenario with BPMs.
But I am getting error while looking into SXMB_MONI.
Under "Monitor for Processed XML messages"
Number of XML message Found 3 (which is my input 3 xmls which is fine) but
"Status is RED Flag".
"Error Category: BPE_ADAPTER"
"Error ID: UNKNOWN_MESSAGE".
Please help me out with this problem.
Regards
Sam

Hi Raj,
When i click PE getting following error:
"Unable to perform action for selected message".
When i double click the row, it takes me to xml message versions where i can RED FLAG for "Call Adapter". In the trace i foudn the below at the end:
<trace level =1 type=system error> error exception return from pipeline processing"</trace>
Hope this helps to guide me mroe
sam

XI BPM Collect Meassages Scenario with one Message as an optional

Hi guys,
I need help to implement XI BPM Scenario with Collect Messages Pattern. Here is my Scenario. I am getting four different types of flat files from four interfaces. Using these four files I need to merge using correlation relation and finally have to create One IDoc type to send it to SAP R/3.
But out of these four messages last Message type is an Optional Message. i.e the process has to continue even if forth message is not available by taking first three messages.
Please let me know which pattern is suitable for this scenario.
Thanks.
Siva.

Hi,
I hope u are receiving four different interfaces.Have a local container variable of simple type integer.you put a fork with four branches after the start step.Each branch has a receive step corresponding to one interface. Then after each of the receive step in each branch put a container operation performing some action on the container variable may be incrementing.so in the end condition of the fork check the value of the container variable i.e you can check if that variable is 3(three of the interfaces have been got).so this ensures that ur fork doesnot wait for all the four.hope this works.
Regards,
Sudharshan

Clariffications in MM SUS Scenario with ECC 6.0 backend and SRM 5.0

Dear Team,
We are implementing MM SUS Scenario with ECC 6.0 backend and SRM 5.0
We need to following clarifications
1 Once we create ASN in SUS, how to cancel the ASN. We are not able to see cancel button for ASNs
2 When we create GRN in ECC against the inbound delivery and perform Return Delivery, this Return Delivery is getting updated in SUS. But the ASN status is not changing to canceled. We are not able to perform new ASN for this. Also invoice is being allowed for these ASNs. How to control the same.
Request your inputs please
Regards,
Ravi

HI can you tell me how you get it solve?
thanks in advance.

EDI Scenarios

Hi,
With regarding to EDI scenarios with XI and seeburger, would like to get input on the following.
As the technical stuffs of conversion can be done with seeburger, is it easy or hard to prepare the mapping specifications from EDI to idoc xml.
Do we require functional knowledge to prepare EDI mapping?
I believe as most of the standards are available in internet, it is going to be just one to one mapping .
Do let me know the challenges ahead on preparing edi mapping.

Krish,
My experience says it is a combination of both funtional and techincal experience required. Technically you can google it and can know what each field. But functionality wise you may need to take the help of functional consultnat because of all the looping in the EDI. If you know that it should not be a big problem in writing the mapping specification.
You can find some techincal help here :
http://www.tsilogistics.com/edi.htm
Regards,
---Satish

Implementation guide for VDERP with EWM = 9.0 (PbV Standard) available?

Hi,i'm an EWM developer and want to implement a VDERP scenario with the EWM 9.0 PbV standard screens.I already have setup the ViceArtisan and the PT. -How do I get the Attribute files for the standard screens - do i need to write them manually or can they be created from the screens? - What steps do I have to do to create a suitable VC Application? Kind Regards

Hello,Attached are the HTML templates, required voice attribute files and other config files. These should help you to navigate through SAP EWM standard PBV transaction. For directions on how to setup these files, kindly follow the Voice Direct ERP implementation guide. For your second question, we are working on a custom built HTML generator, which would help generate HTML template as required by VDERP with very less to no changes to any SAP RF screen. An Alpha version of the same has been released (SAP Transport) with appropriate documentation on how to use it. Let us know if you need access to it? Thanks.

Webinar: How to implement secure scenarios with SAP NW PI 7.1

SAP Intelligence Platform & NetWeaver RIG APJ Expert Call
Dear valued SAP Experts,
Next SAP Intelligence Platform & NetWeaver RIG Expert Call Session will take place on Tuesday, August 18.
The SAP Intelligence Platform & NetWeaver RIG Expert Call Sessions are designed to support consultants, partners and customers during their implementation projects. The sessions cover all different aspects of SAP NetWeaver and are aimed at
thus provide knowledge which is not available via standard training courses. The session duration is typically 60min and includes questions and answers.
Tuesday, August 18, 2009:
How to implement secure scenarios with SAP NetWeaver Process Integration 7.1
Time: 2.00 - 3.00 p.m. Singapore Time (UTC +8)
This event will feature Makoto Sugishita with the SAP Intelligence Platform & NetWeaver Regional Implementation Group.
Makoto provides the following abstract:
In this session you will learn more about the core security concepts that are provided with the service-oriented architecture (SOA)
management capabilities in SAP NetWeaver Process Integration (SAP NetWeaver PI). This session will cover main use cases and
supported scenarios of secure SAP NetWeaver PI deployments.
SAP Connect Link: https://sap.emea.pgiconnect.com/I016095
(no passcode needed)
Dial in:
For dial in details please register here http://www.surveymonkey.com/s.aspx?sm=EFeuZl9PxrwKOW5i5W556g_3d_3d
Kind regards,
Sarma Sishta
SAP Intelligence Platform & NetWeaver RIG APJ

hi,
I'm making this a sticky thread till August 18 so it will have better visibility
Regards,
Michal Krawczyk

Message mapping challenge in IDOC to EDI scenario

Dear PI message mapping experts,
I'm a newbie in PI and facing a mapping problem using graphical message mapping.
I'm in an IDOC (INVOIC.INVOICE02) to FILE (EDI) scenario.
Here after is the mapping i need to perform :
Source structure IDOC :
<E1EDKA1> (0..99)
   <NAME1> A </NAME1> (0..1)
   <NAME2> B </NAME2> (0..1)
   <NAME3> C </NAME3> (0..1)
   <NAME4> D </NAME4> (0..1)
</E1EDKA1>
Target structure :
<AccountingCustomerParty> (1..1)
   <Party> (0..1)
      <PartyName> (0..unbounded)
          <Name>A</Name> (1..1)
      </PartyName>
      <PartyName>
          <Name>B</Name>
      </PartyName>
      <PartyName>
          <Name>C</Name>
      </PartyName>
      <PartyName>
          <Name>D</Name>
      </PartyName>
   </Party>
</AccountingCustomerParty>
I know i have to play with context and queues with stanard function or UDF but cannot succeed to do it.
Could you please help me ?
Thanks in advance,
Alysee

One approach out of available few ways to implement this:
NAME1 - Exists - CreateIf - PartyName[0]
NAME2 - Exists - CreateIf - PartyName[1] (Create deuplicate segment)
NAME3 - Exists - CreateIf - PartyName[2] (Create deuplicate segment)
NAME4 - Exists - CreateIf - PartyName[3] (Create deuplicate segment)
Srikanth Srinivasan

File to multiple IDOCs scenario with the same receiver system

Hi guys,
I have to design and implement the following scenario:
I will receive one file with many lines (Records) with data for materials, quantities, operations etc..
Based on the values of some fields of each line, I will have to create an IDOC for each material.
For example:
if operation type = "INSERT", and Labor = 001 then create 3 Idocs of type MBGMCR with movement types=101, 261,311 that have to be posted one after the other to the same receiver system.
else if operation type = "INSERT", and Labor <> 001 then create an Idoc MBGMCR with movement type=311 and plant = 1001.
else if operation type = "Delete", and Labor = 001 the created 3 Idocs MBGMCR with movement type=312, 262 1002 and post them serially to the same receiver system.
else if operation type = "Delete", and Labor <> 001 the created 1 Idoc MBGMCR with movement type=312.
All IDOCS are posted to the same SAP R/3 system. We do not care about the sequence, except for the cases where 3 IDOCS are created.
I am trying to think of a good design in performance terms.
It is obvious that I will need BPM for sure.
I am thinking of creating a mapping program that will produce 4 message types for the different cases from the initial file and then create a different message mapping for each case from the message type to the IDOC.
I am asking you if I have to include everything (mappings) in BPM with a "fork" step?
Or shall I produce only the 4 message types and then post them to R/3 and execute the mappings in R/3?
Best Regards
Evaggelos

hi,
>>I am thinking of creating a mapping program that will produce 4 message types for the different cases from the initial file and then create a different message mapping for each case from the message type to the IDOC.
To me this seems to be the right solution.
here u will create different message mappings and write them sequentially in interface determination. the multi mapping will then be utilised in transformation step in BPM.
thus if this is the only requirement there is no need of using a fork step.
[reward if helpful]
regards,
latika.

File To Mail Scenario With An Attachment

Hi All,
I Want to Implement a FileXI--Mail Scenario With An Attachment
I Want to Send a Text File From the File System As An Attachment to the Mail.
Can We Do this With out Doing JAVA Or XSLT Mappings in this ???
Please Give me the Steps That I Have to Follow
Regards
Babu

Babu,
I am not sure how complex is your file sturcture and the mapping. But we can also achieve without java or xslt mapping also. Please check these weblogs:
/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
Also you have to use module swap for sending the attachment as txt file. Please check this weblog for this:
/people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0964d7c-e66e-2910-24bb-ac535e4a5992
Regards,
---Satish

Idoc to edi scenarios (mapping help is required)

hi expects ,
    i am working on idoc to edi scenarios in which i am using seeburger abapter.and i have to use java mapping with using some standard function.
INPUT IDOC :
                    Name                         M/C     Min Use      Max Use        Description
INPUT*                                              M               1           1
Record EDI_DC40*                                 C               0           1                       Control Record
Record E2EDK01*                                  C               0           1                       Document Header General Data
     Record E2EDK14*                                  C               0          12                       Header Organizational Data
     Record E2EDK03*                                  C               0          10                       Header Date Segment
Record TEMP_DATE*                                C               0           1                       Temporary Date Segment
     Record DEL_DATE*                                 C               0           1                       Temporary Date Segment
     Record E2EDK04*                                  C               0          10                       Header Taxes
Record E2EDK05*                                  C               0          16                       Header Conditions
Record E2EDKA1*                                  C               0       99999                       Header Partner Info
Record TEMP_SHIP_TO*                             C               0           1                       Ship-to Info
Record TEMP_SOLD_TO*                             C               0           1                       Sold-to Info
Record TEMP_PAYER*                               C               0           1                       Payer Info
Record TEMP_CARRIER*                             C               0           1                       Carrier Info
Record TEMP_DISCHARGE_PORT*                      C               0           1                       Port of Discharge info
     Record TEMP_NOTIFY*                              C               0           1                       Notify Info
Record TEMP_NOTIFY_ALSO*                         C               0           1                       Notify Also Info
Record TEMP_EXIT_PORT*                           C               0           1                       Port of Exit Info
Record TEMP_CONSIGNEE*                           C               0           1                       Consignee
Record TEMP_SHIPPER_INFO*                        C               0           1
Record E2EDK02*                                  C               0          10                       Header Reference Data
     Record TEMP_E2EDK02*                             C               0           1                       Temp E2EDK02
Record TEMP_PO_STRING*                           C               0           1                       TEMP PO STRING
Record E2EDK17*                                  C               0         999                       Header Terms of Delivery
     Record TEMP_E2EDK17*                             C               0           1                       Temp transportation terms
     Record E2EDK18*                                  C               0          99                       Header Terms of Payment
     Record TEMP_TERMS*                               C               0           1
Record E2EDK35*                                  C               0          10                       Additional Data
Group E2EDKT1:2*
OUTPUT FIELD:
Segment B2*                                      M               1           1                       BEGINNING SEGMENT FOR SHIPMENT INFORMATION TRANSACTION
     Segment B2A*                                     C               0           1                       SET PURPOSE
Segment N9:6*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:7*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:8*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:9*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:10*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:11*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment CUR*                                     C               0           1                       CURRENCY
Segment ITD*                                     C               0           1                       TERMS OF SALE/DEFERRED TERMS OF SALE
     Group DTM_GROUP*                                 C               0           1
Segment DTM*                                  C               0           1                       DATE/TIME REFERENCE
Segment DTM:2*                                C               0           1                       DATE/TIME REFERENCE
Segment DTM:3*

Hi,
To do the mapping,,,,even you can go for graphical mapping....
But some of the context handling issues you need to deal with,
like....
1.Never map set context of source fields to element level but Segment level.
2. Always you need to check for qualifiers while mapping it to Traget field.
Thanks & Regards
Akshay.
Dont Forget TO Give Points.

EDI interface with MM

Hi Gurus,
I want to have detailed information on EDI interfaces with MM. A detailed explanation will be highly appreciated.
thanks,
Kumar

Hi
EDI interface with MM can be anything that may be required as per the scenario needed. Any interface to SAP from legacy using EDI application. The most imagined interface can be Say there is a third party system in which Purchase orders or Req are entered by different Buyers and those need to be interfaced to SAP for creating the orders in SAP.
Similarly another thing that can be imagined is Material movements posting from a third party warehouse system
Please let me know if you have any specific question on this.
Thanks

Design Approach for 1:N Multimapping scenario with SAP ECC Receiver

Hi Experts,
I am trying to find the best approach to implement the following scenario. its desribed as follows:
Legacy Database ->XI -> SAP scenario.
1. Pick records from database table with status ='n'
2. The records picked can have one or more RefNos i.e. if 2000 records are picked 1500 can have RefNo :1111 and rest 500 RefNo: 2222
3. 1st condition is to split the records into multiple messages if reference nos are different, so for scenario in point 2 it will be 2 messages. Secondly if the no of records are more than 1000 then split further into 2 message. So 1500 Ref No would be split into messages with 1000 and 500 records. Hence we get 3 messages. I know something similar was achieved in this blog:
</people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool
4. Once the data is forwarded to ECC and its successfully updated, we need to update the status of the database table on the sender side to 'y';
So the point where i am not very clear as of now is,
1. What alternative I choose for PI-> ECC call? Its a 1:N multimapping split scenario and as far as I know the call has to go via AE, so is RFC the only option or is there a way to have a call with Proxy/IDOC? Or will there be an option to limit such a scenario at the JDBC Adapter level so that split is not needed. I am not sure if that can be achieved and is a better solution.
2. If I go for either of the approaches mentioned above, what is the best way to achieve point 4, i.e. update the database table at the sender. As JDBC Adapter would be async and hence we either use a Aysnc-Sync bridge(for proxy/rfc receiver) or some other option like triggering a outbound interface from SAP side with the update data?
Hope that experts can provide the inputs on the best way forward.Let me know if anything is missing from scenario details perspective.
Best Regards,
Pratik

Pratik,
2. If I go for either of the approaches mentioned above, what is the best way to achieve point 4, i.e. update the database table at the sender. As JDBC Adapter would be async and hence we either use a Aysnc-Sync bridge(for proxy/rfc receiver) or some other option like triggering a outbound interface from SAP side with the update data?
Use the solution # 2, make it like this:-
DB (async) -> PI -> Proxy (sync) -> PI -> DB (async)
Just out of curiosity, why you breaking the records into 1000's in PI? Why not you select only 1000 records when polling the DB? That will help in improving the overall performance.
Regards,
Neetesh

AS2 Adapter EDI scenario - question

I am working on a EDI scenario, involving AS2 adapter.
Could anyone tell me any steps to be done on ABAP engine.
reg

Hi Naveen,
follow the below steps:
1) First deploye the Std seeburger mapping provided by see burger on XI
2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.
3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.
5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.
steps in IR and ID.
In IR:
You need to use the Standard XSD provided by Seeburger for different mesages like EDFACT ORDERS D96A etc in IR and other steps are similar which we do for the normal scenarios.
In ID:
This is the scenario for AS2
Seeburger has provided std mapping which need to be deployed on Xi server and will be used in XI adapter module tab for EDI-XML and XML-EDi conversion.
Example of mapping:
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
1) After deploying mapping program.
We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.
1)The value of the Agency field must be Seeburger.
2)The value of the Schema field must be AS2ID.
Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab
Configuration in adapter:
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Sender AS2 adapter configuration:
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
You can refer my thread reply:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.
EDI-SEEberger-XI-IDOc-R/3
flow of the data from EDi to SAp r/3 using seeburger:
1) Data will be coming thorugh WAN or mailbox.
2) If its coming through WAN then every WAN provider will give the partner which is sending the data a partner number for indentification.
3) In your AS2 channel you need to configure the party and for that party you need to give the WAN number which is proivded for that partner. So it will run that configuration whenever that partner send the data.
4) In the adapter you have to give the mapping program name which does the conversion of EDI-XML and XML-EDI.
5) Once you XML is generated then it will be used in MM
6) At the receiver if its IDOC adapter then IDOC adapter will post the IDOC to R3 system.
Thnx
Chirag

Implementing an EDI scenario with XI

Similar Messages

Maybe you are looking for