Walmart integration

[Former Member]

Dear experts,

I need to understand EDI better.

Recently i got a document from Walmart.

We need to do implementation being a supplier to walmart.

Walmart will send us Purchase order and we need to create Sale order.

Further they have mentioned we need to obtain gem mailbox and

do as2 exchange of information.

On other side they have written sender pushes purchase order to reciever being walmart.

I am bowled out to understand if i need to connect to mailbox from my own to read purchase orders or is it

that i have to wait for purchase orders to come to my edi subsystem which may be SAP PI/PO

and do further handling with B2B addon or Seeburger something ?

Document has a dual information or somewhere i lack in concept.

Has anybody face this scenario.Kindly respond.

I will be glad if someone is already engaged in such business flow and explain here.

Regards.

Aditya Sharma

[Dimitri]

Hi Aditya,

I will try to describe the scenario once more...

Prerequisites:

• B2B add-on installation and configured properly. Please refer to
  
• ESR objects in place

Scenario: Walmart --> AS2 --> SAP PI --> SAP back end

Basically, you will have 2 scenarios:

1. Get the Walmart file and receive is. Optional: produce an acknowledgment
2. Process the received file and produce an idoc

Get the Walmart file and receive is. Optional: produce an acknowledgment

You need a sender AS2 communication channel configured. Refer to for some leads.

Also, configure a receiver EDIseparator communication channel with the option to generate an acknowledgement(*) message.

The Sender AS2 communication channel will produce a MDN (Message Delivery Notification) message. That is proof for Walmart the message was technically received by SAP PI.

This step does not require a message mapping within the ESR

(*) in case you go for an acknowledgement message being send back to Walmart, you need to configure an extra sender EDIseparator communication channel and a receiver communication channel to process this acknowledgement message.

Process the received file and produce an idoc

You need a sender EDISeparator communication channel configured where you can only allow Walmart messages or you can use a generic one for all EDI interchanges entering the system.

You also need a receiver IDOC communication channel to process the messages to your SAP back end system.

This step requires a message mapping (XML -> IDOC) within the ESR

Of course, you need to create extra objects within the Integration Directory part, besides the different communication channels.

- Your mission -

Try to understand the concept and figure out what you need to build. Do that on paper first.

Next step is building all the blocks (objects) and create your communication channels.

Please revert back if any specific problem or error pops up.

Hope this clarifies.

Kind regards,

Dimitri

[Former Member]

Thanks Dmitri for the response.I have tried creating some objects as discussed.But frankly they are all independent objects configured in relevant sections.In order to make them work together ,is it mandatory to use configurator ie colored pie icon.

I need clarity on how things work as whole.I recall one video where i saw complete scenario design in netweaver studio .Where exactly can we do same in ESR.I went to create scenario and tried to edit component window there.Right clicked to add Application component.Finally ended up getting whole product on layout window.This is not i am looking for prehaps.

[Former Member]

Throwing some more light on previous post.

I can also see Integration flow,but the option is coming disabled.

Should this be my hitpoint and should i get same activated by talking to basis.

Regards.

Aditya.

[Dimitri]

Hi Aditya,

Again, you are mixing things up...

You can use iflows (create scenarios using the NetWeaver Development Studio). In that case you have the ESR and ID in 1 single view.Or you can use the classical way via the Integration Builder.

Both are standard stuff and you can find lots of information on this forum or within the SAP help.

Kind regards,

Dimitri

[Former Member]

Dmitri,can i have your mail id to share some resources for understanding better ?.I am not able to upload file here

[Dimitri]

Hi Aditya,

My e-mail address is made public. You can find it attached to my SCN ID.

Please note that I will share all information within this thread or refer to a new thread in case space is getting limited here.

Also, do read carefully and do not publish my e-mail address within a thread.

Kind regards,

Dimitri

SCN moderator

[Former Member]

Dmitri,

I have just recently send an email to you mentioning steps performed by me.

I am sure ,i may be wrong,so need your suggestion to proceed.

Regards.

Aditya Sharma

[Former Member]

Hi Dmitri,

It makes me believe that i have to create integration configuration after been able to go inside this option.

Now , as per your direction i am not able to define communication channel linkage for recieving and outbound.

I tried:

1.  AS2SENDER TO EDISEPREC (Reciever)

2. But i cannot do then EDISEPREC (Reciever) to EDISEPREC (Sender)

Pl help.Also will be great as you find time to look on document that i send you by mail yesterday.

Regards.

Aditya Sharma

[Former Member]

but i believe if i take EDISEPREC communication channel to be sender again ,i could achieve.Do i need to do that ?

[ruchir_sinha]

Hi Aditya,

Sorry to interrupt the conversation but you need not do the 2nd step separately i.e. no need to create an ICo between EDISeparator Receiver with EDISeparator Sender.

In you case following will be the ICo's

ICo 1: AS2 Sender channel <-->  EDISeprator Receiver channel

ICo 2: EDISeparator Sender channel <--> File Receiver channel

Regards,

Ruchir

[Former Member]

Thanks  Ruchir.I have created this way.

The fact is ,at this stage i cannot test scenario on my own because i have to ask walmart to push the file from there.Before doing that i have to be very sure that whatever i have done is correct or not.

1. In light of same ,i wish to tell you that i was able to retrieve the list of interfaces while creating ICo

when i set both fields "any" ie business system and category .If even i select Business system as PO server and category "any", i retrieve nothing.

I checked SLD and found my product was well attached.Is this normal way to set both "any" and then proceed creating Ico.

2.Do i need to create communincation channel for EDISeparator reciever.If yes then why not in integration configuration we are not supposed to define from ediseparator sender to ediseparatore reciever relation as told by you ?.

I can send you all changes made as of now incase you can update your mail id.

Regards.

Aditya Sharma

[Former Member]

Anyways,is there some wasy way by which i can map source field = target field of .xsd both at source and target.This .xsd is a huge number of fields file.Equating each graphically is a challenge and laborious too.

[Dimitri]

Dear Aditya,

Again, I really need to stop you here.

People are trying to help you, please do read their answers and try it out.

I see that you are still asking a lot of basic PI/PO questions and people's answers are clear: do search on SCN before you post. Within this context, I refer again to the SCN Rules of Engagement.

For the reasons above, I will lock this thread.

Thank you.

Dimitri

SCN moderator

NOTE: think about the e-mail you've sent me and try to figure out things yourself, using the SCN as a valuable source. Try to set up the scenario, using iflows or the classical way, and test the EDI conversion within the B2B add-on.

In case specific problems pop up, please open a new thread explaining your problem in detail.

[Harish]

Hi Aditya,

Please refer the below document.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0e1d976-27df-2f10-06b2-d151201fc...

B2B RDS integration

B2B EDI inbound integration

regards,

Harish

[Former Member]

Harish,

Thanks for the help.I already have this article .But we are using SAP PO and this one is for PI.

Going further in inbound scenario ,I couldnot figure out if we need to create any mappings or structures of source or target.

Regards,

Aditya

[Dimitri]

Hi Aditya,

SAP Process Integration and Process Orchestration are basically the same for what B2B integration is concerned.

Please read several articles concerning the B2B add-on within this community and will have a clear view what is all about.

Off course you will need mappings etc, but with the B2B add-on from SAP, this is easier than e.g Seeburger software.

Kind regards

Dimitri

[Former Member]

Thanks Dmitri as once again you have come to rescue.Infact your contribution to all members has been awesome. See what i am thinking is what will be my source structure.Target i can put later as idoc though.How will i know how EDI Separator is going to percieve my file into what sort of structure.

[Dimitri]

Hi Aditya,

To have an idea, start reading

Once you come across step 5, read more careful.

Bottom line is defining your incoming EDI message structure based on

• content SAP delivers
• your own message structure

The configuration of your sender EDISeparator adapter + control keys in the EDI content manager = the key for converting the incoming EDI message to XML. No other mapping is required.

Off course, you need a message mapping within the ESR if you want to map to an idoc.

Your source structure within the ESR = the XSD, exported from the EDI content manager and imported as External Definition object.

Kind regards,

Dimitri

[Former Member]

Dear Dmitri,

I go to b2bic link.

nclude syntax notes:
Include semantic notes:
Include comments:
Namespace: *
Control key name: *
Enable batch message support:
Maintain compatibility to previous releases:

Set: *
Version: *
All versions:

Start

What to give in set ?? version ??

[Former Member]

Also when using cockpit i try to convert edifact->xml ,i get this

message below.

Sample file i have from walmart is:

UNB+UNOA:2+925485IN00:8+007997:1+130916:1505+1'UNH+1+ORDERS:D:96A:UN'BGM+220::9+PO number +9'DTM+137:20130916:102'DTM+43E:20130923:102'DTM+10:20130916:102'FTX+SPH+++NO PRETICKET'RFF+SD:61'RFF+ZZZ:20'RFF+PD:REPLENISH'NAD+BY+8903192000044::9++BHARTI WAL-MART PVT LTD CNC 4702'NAD+SF+++Company Name'RFF+IA:007997610'CUX+2:INR:9'PAT+1++21:3:D:21'TDT+20++30+31+:::VENDOR ROUTE'TOD+6+PO'LIN+1++000089002940:UP'PIA+1+610594549:IN+701467:VN'IMD+C+98+100ML::92'IMD+F++:::Item description'IMD+F++:::100ML/PK OF 3'QTY+21:64'MOA+203:'PRI+AAB:::EUP::EA'PAC+64+3'PAC+1+1'

java.lang.NullPointerException: while trying to invoke the method com.sap.aii.converter.edixmlconvertercomp.wdp.IPrivateEdifact2XMLView$IInterfaceConfigurationElement.getActionName() of a null object returned from com.sap.aii.converter.edixmlconvertercomp.wdp.IPrivateEdifact2XMLView$IContextNode.currentInterfaceConfigurationElement()

    at com.sap.aii.converter.edixmlconvertercomp.Edifact2XMLView.onActionConvert(Edifact2XMLView.java:259)

    at com.sap.aii.converter.edixmlconvertercomp.wdp.InternalEdifact2XMLView.wdInvokeEventHandler(InternalEdifact2XMLView.java:262)

    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)

    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)

    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)

    ... 62 more

See full exception chain for details.

Failed to process request. Please contact your system administrator.

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.

Correction Hints

Exception could be caused by the development component: sap.com/b2b~home

Note: The above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.

System Environment

Client

Web Dynpro Client Type	AJAX Client
User agent	Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.107 Safari/537.36
Client Type	safari
Client Type Profile	sf3
ActiveX	disabled
Java Applets	enabled
Accessibility mode	disabled
Inline CSS	false
Validate by rendering	true

Server

Web Dynpro Runtime	vendor: 'sap.com', name: 'tc/wd/webdynpro', scV: 'sap.com', scN: 'WD-RUNTIME', location: 'SAP AG', counter: '7.4005.20131121163250.0000', R: '7.40', SP: '5', PL: '0', change number: '605350', codeline: NW731CORE_10_REL
J2EE Engine	7.40.3301.351782.20131015082828
System ID (SID)	POP
Server Node ID	|9088650|90886|Server 00 00_90886|dbrtst/172.26.5.228|SERVER|RUNNING
Java VM	SAP Java Server VM, version:6.1.059 24.45-b08, vendor: SAP AG
Operating system	HP-UX, version: B.11.31, architecture: ia64

Application

Java EE Application (deployable object)	sap.com/b2b~home
Web Dynpro Application	B2BHome
Request URI	/webdynpro/resources/sap.com/b2b~home/B2BHome
Version	vendor: 'sap.com', name: 'b2b/home', scV: 'sap.com', scN: 'PIB2BTOOLKIT', location: 'SAP AG', counter: '1.0002.20140102093455.0000', R: '1.00', SP: '2', PL: '10', change number: '519152'

Session &amp; Other

Session Locale	en_GB
Session Timezone	India Standard Time
Time of Failure	Wed Feb 05 16:53:48 IST 2014 (Java Time: 1391599428957)
Session User	ClientUser(id=USER.PRIVATE_DATASOURCE.un:Admin, name=Admin)
Http Session Id	a4SU5Nan_3-WqeR1UH3q0pFijvsARAGKrooA_SAP
Client Window Id	ef148fd78e5711e3b7140000008aae8a
Application Session Id	ef148fd88e5711e3aa580000008aae8a

Web Dynpro Code Generation Infos

sap.com/b2b~home
WD web module webdynpro/resources/sap.com/b2b~home: SapDictionaryGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:41+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/b2b~home: SapDictionaryGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:53+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/b2b~home: SapGenerationFrameworkCore	7.1100.20120918122507.0000
WD web module webdynpro/resources/sap.com/b2b~home: SapIdeWebDynproCheckLayer	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:43+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/b2b~home: SapMetamodelCommon	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:48:33+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/b2b~home: SapMetamodelCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:47:05+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/b2b~home: SapMetamodelDictionary	7.1100.20120918112507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:57:01+0000, changelist=156102, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/b2b~home: SapMetamodelWebDynpro	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:01:46+0000, changelist=155949, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/b2b~home: SapWebDynproGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:52+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/b2b~home: SapWebDynproGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:15:08+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/b2b~home: SapWebDynproRuntimeGen	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:12:14+0000, changelist=188231, host=PWDFM305, is-central=true)

sap.com/converter~maintain~maintenance-app
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapDictionaryGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:41+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapDictionaryGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:53+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapGenerationFrameworkCore	7.1100.20120918122507.0000
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapIdeWebDynproCheckLayer	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:43+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapMetamodelCommon	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:48:33+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapMetamodelCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:47:05+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapMetamodelDictionary	7.1100.20120918112507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:57:01+0000, changelist=156102, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapMetamodelWebDynpro	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:01:46+0000, changelist=155949, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapWebDynproGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:52+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapWebDynproGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:15:08+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/converter~maintain~maintenance-app: SapWebDynproRuntimeGen	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:12:14+0000, changelist=188231, host=PWDFM305, is-central=true)

sap.com/nro~maintenance
WD web module webdynpro/resources/sap.com/nro~maintenance: SapDictionaryGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:41+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/nro~maintenance: SapDictionaryGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:53+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/nro~maintenance: SapGenerationFrameworkCore	7.1100.20120918122507.0000
WD web module webdynpro/resources/sap.com/nro~maintenance: SapIdeWebDynproCheckLayer	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:43+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/nro~maintenance: SapMetamodelCommon	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:48:33+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/nro~maintenance: SapMetamodelCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:47:05+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/nro~maintenance: SapMetamodelDictionary	7.1100.20120918112507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:57:01+0000, changelist=156102, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/nro~maintenance: SapMetamodelWebDynpro	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:01:46+0000, changelist=155949, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/nro~maintenance: SapWebDynproGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:52+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/nro~maintenance: SapWebDynproGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:15:08+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/nro~maintenance: SapWebDynproRuntimeGen	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:12:14+0000, changelist=188231, host=PWDFM305, is-central=true)

sap.com/oftp2~log~web
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapDictionaryGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:41+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapDictionaryGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:53+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapGenerationFrameworkCore	7.1100.20120918122507.0000
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapIdeWebDynproCheckLayer	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:43+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapMetamodelCommon	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:48:33+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapMetamodelCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:47:05+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapMetamodelDictionary	7.1100.20120918112507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:57:01+0000, changelist=156102, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapMetamodelWebDynpro	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:01:46+0000, changelist=155949, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapWebDynproGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:52+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapWebDynproGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:15:08+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/oftp2~log~web: SapWebDynproRuntimeGen	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:12:14+0000, changelist=188231, host=PWDFM305, is-central=true)

sap.com/tc~wd~api
WD web module webdynpro/resources/sap.com/tc~wd~api: SapDictionaryGenerationCore	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T22:13:29+0000, changelist=397622, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapDictionaryGenerationTemplates	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T22:13:35+0000, changelist=397622, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapGenerationFrameworkCore	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T21:24:40+0000, changelist=397649, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapIdeWebDynproCheckLayer	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T22:46:36+0000, changelist=603569, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapMetamodelCommon	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T21:26:04+0000, changelist=397782, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapMetamodelCore	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T21:24:56+0000, changelist=397782, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapMetamodelDictionary	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T21:53:28+0000, changelist=397624, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapMetamodelWebDynpro	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T22:16:48+0000, changelist=603570, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapWebDynproGenerationCore	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T22:47:15+0000, changelist=603569, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapWebDynproGenerationTemplates	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T22:47:03+0000, changelist=603569, host=pwdfm849, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapWebDynproRuntimeGen	7.4005.20131031110849.0000 (release=NW731CORE_10_REL, buildtime=2013-11-29T22:37:52+0000, changelist=605349, host=pwdfm849, is-central=true)

sap.com/tpm~uimain
WD web module webdynpro/resources/sap.com/tpm~uimain: SapDictionaryGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:41+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/tpm~uimain: SapDictionaryGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:02:53+0000, changelist=145689, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/tpm~uimain: SapGenerationFrameworkCore	7.1100.20120918122507.0000
WD web module webdynpro/resources/sap.com/tpm~uimain: SapIdeWebDynproCheckLayer	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:43+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/tpm~uimain: SapMetamodelCommon	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:48:33+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/tpm~uimain: SapMetamodelCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:47:05+0000, changelist=146159, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/tpm~uimain: SapMetamodelDictionary	7.1100.20120918112507.0000 (release=NW711_08_REL, buildtime=2012-09-20T14:57:01+0000, changelist=156102, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/tpm~uimain: SapMetamodelWebDynpro	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:01:46+0000, changelist=155949, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/tpm~uimain: SapWebDynproGenerationCore	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:14:52+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/tpm~uimain: SapWebDynproGenerationTemplates	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:15:08+0000, changelist=180073, host=PWDFM305, is-central=true)
WD web module webdynpro/resources/sap.com/tpm~uimain: SapWebDynproRuntimeGen	7.1100.20120918122507.0000 (release=NW711_08_REL, buildtime=2012-09-20T15:12:14+0000, changelist=188231, host=PWDFM305, is-central=true)

Detailed Error Information

Detailed Exception Chain

java.lang.NullPointerException: while trying to invoke the method com.sap.aii.converter.edixmlconvertercomp.wdp.IPrivateEdifact2XMLView$IInterfaceConfigurationElement.getActionName() of a null object returned from com.sap.aii.converter.edixmlconvertercomp.wdp.IPrivateEdifact2XMLView$IContextNode.currentInterfaceConfigurationElement()

  at com.sap.aii.converter.edixmlconvertercomp.Edifact2XMLView.onActionConvert(Edifact2XMLView.java:259)

  at com.sap.aii.converter.edixmlconvertercomp.wdp.InternalEdifact2XMLView.wdInvokeEventHandler(InternalEdifact2XMLView.java:262)

  at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)

  at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)

  at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)

  at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)

  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)

  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)

  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)

  at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)

  at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)

  at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)

  at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)

  at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)

  at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)

  at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)

  at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)

  at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

  at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)

  at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

  at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

  at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:367)

  at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:490)

  at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:73)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

  at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

  at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)

  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

  at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

  at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

  at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

  at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

[ruchir_sinha]

Hi Aditya,

It looks like you are trying to use ANSI X12's XSD generator. In order to generate the XSD you first need to import the ANSI X12 B2B seed file. This is shipped along with B2B Addon and available on Service Marketplace. After the B2B file is imported then you can generate the XSD for given set and version of ANSI X12.

Same goes for EDIFACT as well.

Regards,

Ruchir

[ruchir_sinha]

Hi Aditya,

After you import the EDIFACT B2B file (above reply). Then you need to define an association in Scenario Association UI between your PI scenario and the SAP shipped control key. After this you can perform conversion from the UI.

Regards,

Ruchir

[Former Member]

How can i get the seedfile ?.I need for EDIFACT.

[Dimitri]

Hi Aditya,

Please do read again and verify if you have all that. This is specifically for EDI sccenarios.

Kind regards,

Dimitri

[Former Member]

Hi Dmitri,

Nice to see your response. Finally I have got the data to tables for desired EDI standards .For me I have done on ANSI X.12 and EDIFACT.After this I tried convert option of File->XML.Right now the file which walmart has given me as sample doesnot look correct.I cant share here as it is confidential.File which walmart has given me looks to be on EDIFACT.I say so because it starts with UNB+UNOA.Still I tried to add a sample file finding from internet and it got successfully converted.

I will obtain correct file from Walmart.Then go with repository process

Meanwhile Dmitri and all other PO members,i wish to discuss my scenario among all of you.

Scenario is : AS2 connection between sender and receiver.Walmart is sender,we are receiver of purchase order.On receiving Purchase order,we need to convert same to a sale order.

For this at present ,other than establishing AS2 at very beginning,i have opted to use FTP path where I will place a text file of same format of purchase order.File will be picked from FTP path and after getting routed through EDI Separator will be mapped to corresponding one to one field on target structure which will be an idoc ORDERS05.

Once I am convinced with results of FTP ,I will substitute same by AS2.

Am I going in right way ?

[Former Member]

Following my scenario,i need to understand that when i get my purchase order file from Walmart,

I need to configure EDISeparator  communication channel, AS2 B2B channel separately as two

recievers ?.If so how will the sequence be maintained that first goto EDISeparator and then to B2B

AS2.Is there some modelling to be done.

[Dimitri]

Hi Aditya,

E.g you can configure an AS2 sender CC to get EDI files into the system.

You also need a receiver EDISeparator adapter to process that incoming EDI interchange.

Next to that, you need a second EDISeparator adapter, but in this case a sender one.

There you decide your routing via e.g GLN number.

You also need a receiver adapter to process the individual EDI message, e.g IDOC, file, ...

Something like this:

Kind regards,

Dimitri

[Dimitri]

Hi Aditya,

Check my answer on your other question.

AS2 -> SAP PI -> Idoc on SAP back end system.

That is a good scenario you can further explore and use.

Kind regards,

Dimtri

[Former Member]

I have some confusion in going for further config.Till now i have defined same mapping

ORDERS99B.xsd in source as well as target .I expect whatever i will get in source will result out file in ftp path as i have equated all fields in target = source using graphical mapping.This has been a very laborious activity because i have mapped each and every field of segments in source and target considering nested information.

Going forward ,now i think where to start with .I have designed EDI Separator as sender and reciever communication channel.AS2 will be reciever i assumed but after going through document ,it looks i will be sender because decrypt option is in sender.Here i am confused what is sender communication channel.If i send to integration engine ,then i become sender or is it if walmart send me ,i become reciever so i need to set reciever.If i am reciever then why will i encrypt.I am confused.

Also i need to understand after EDI Separator filters out message,how will it convert to xml.Is there some modelling behind this.

Next is where lies EDI separator.Receiver will recieve Purchase order information and sender will do what ?

I cannot understand the concepts mainly even going through the documents.All documents keep assumption that your basics are clear and fact is that this is my first scenario and it starts with Process orchestration.

[Dimitri]

Hi Aditya,

You are mixing up things here...

Please start with SAP PI/PO basics and try to understand the Adapter Engine and the Integration Engine.

Also, try to learn more about the Enterprise Services Repository. E.g.: SAP ships standard content which is ready to use for you within standard scenarios and mappings. This could have saved you several hours.

Next to that, try to understand the scenario and start using the B2B add-on step by step.

It does not make any sense to ask a lot of questions on the SCN forum without understanding the concept behind it. It confuses people and takes time. That time, you could spent in mastering SAP PI/PO and the B2B add-on.

Kind regards

Dimitri

PS1: a sender adapter picks up something and a receiver adapter writes something. That's the best way to remember the difference.

PS2: is a good starting point for your B2B scenario.

Message was edited by: Dimitri Sannen