Reg:Seeburger BIC Error

Hello All,
I was working on XML to EDIFACT Map in BIC Mapping Designer in seeburger,I am getting following Error while running the map:
[Error:ID=3056;LEVEL=1] InhouseDocWriter setField() Error: Exception at create or setField(UNB.SG0.UNH:S009.0065) :
java.lang.Exception: Segment not allowed here (UNB:SG0).
Any one please guide me reg this issue.
Thanks,
Kishore

Hi,
Can you explain about your mapping?
Could you quote your result for message mapping test tab?
Regards,
Sushama

Similar Messages

Reg: Seeburger BIC Mapping Designer

We are using BIC to resolve hierarchy issue.. As you know we can not pasre more than 2 hierarchy levels in XI.
we have a text file which contains all the records in one row..
<Recordset>
 <Record00> 1-unbounded
 <Field>
 <Field>
 <Record01>1-unbounded
 <Filed>
 <Field>
I did following steps in BIC...
Created Datatype in INHOUSE to user project
Edit structure and save
Export structure (msg_....xml)
Run CreateXMLmessage, source file msg_....xml, target file XML_....xml)
Import XML.xml to User Project
Run CreateMappingXMLToEdi source file msg_....xml, target file X2E_....xml
Import X2E.xml to user project..
Run X2E Map by giving our source text file and output will be in xml.
Problems:
 In 5th Step. while importing XML to user project i am getting auto correction window which is changing field occurances and false to true etc.
 In 8th Step i am getting errors with conversion and i got the output xml file but with default values which i have given while creating datatype.
I have gone thorugh all the links related to seeburger.
I would really appreciate if anyone thorw some light on the same.
Thanks in Advance...
Regards,
Mansoor.

Hi
the steps to generatt the file using the BIC is
1.create the structure in inhouse
2.select the structure you have created , right click then go to the Export, give the destination, the file will be saved at that location.
3.now create the XML message using the create XML Message
4.After creating the XML Message import the XML file .
5. After importing the file the file can be see in the XML node in the BIC mapper for the inhouse structure you have created.
in this way you can create the XML file.
and the created xml file you cam export as XSD,as XML. or as DTD
if you still face the problem please reply me back
Thanks
Rinku

Reg:Seeburger BIC

Hello All,
 I am working form xml to EDIFACT Map.based on the number of OrderReason in the input file we must genrate the FTX Segment in the output.
For Example:
If the inputfile looks like:
<OrderReason>
<OrderReasonCode>RSRJCT</OrderReasonCode>
<OrderReasonDescription>Info The order has been rejected by HP-RSAP</OrderReasonDescription>
</OrderReason>
<OrderReason>
<OrderReasonCode>E9850A</OrderReasonCode>
<OrderReasonDescription>Error Price is different from that in HP</OrderReasonDescription>
</OrderReason>
The output must be:
FTXACD++RSRJCT'
FTXAAO++Info The order has been rejected by HP-RSAP'
FTXACD++E9850A'
FTXAAO++Error Price is different from that in HP'
The Condition i was written was not incrementing:
//FTX ACD
if existSourceField("B2BGatewayDoc.Document.ServiceContent.POConfirmationHeader.OrderReason.OrderReasonCode:value") = true
 copy "ACD" to UNB.SG0.UNH.FTX:4451;
 copy B2BGatewayDoc.Document.ServiceContent.POConfirmationHeader.OrderReason[lvORDERREASONCOUNTER%].OrderReasonCode:value to UNB.SG0.UNH.FTX:C108.4440;
 endif
//FTX AAO
if existSourceField("B2BGatewayDoc.Document.ServiceContent.POConfirmationHeader.OrderReason.OrderReasonDescription:value") = true
copy "AAO" to UNB.SG0.UNH.FTX:4451;
copy B2BGatewayDoc.Document.ServiceContent.POConfirmationHeader.OrderReason[lvORDERREASONCOUNTER%].OrderReasonDescription:value to UNB.SG0.UNH.FTX:C108.4440;
endif
lvORDERREASONCOUNTER%=lvORDERREASONCOUNTER%+1;
Can,any one guide me.

Hello Shweta,
 The input file :
<?xml version="1.0" encoding="ISO-8859-1" ?>
<B2BGatewayDoc>
<Document>
<ServiceHeader>
<Protocol>
<Sender>003897733</Sender>
<Receiver>544759087</Receiver>
<MsgType>3A4MG2</MsgType>
<ReferenceNumber>1</ReferenceNumber>
<InstanceIdentifier>455</InstanceIdentifier>
<PipVersion>V02.00</PipVersion>
</Protocol>
</ServiceHeader>
<ServiceContent>
<FromRole>
<ContactName>HP CO OM</ContactName>
<EmailAddress>GOPALKRISHNANV</EmailAddress>
<TelephoneNumber>65-67271815</TelephoneNumber>
</FromRole>
<ToRole>
<ContactName>YANG MINGJIN(IRENE</ContactName>
<EmailAddress>IRENE.YANG-ASIA.COM</EmailAddress>
<FaxNumber>021-24016684</FaxNumber>
<TelephoneNumber>021-24016753</TelephoneNumber>
</ToRole>
<POConfirmationHeader>
<PONumber>SP30-60659-S</PONumber>
<RequestingDocumentDateTime>20100525T120000.000Z</RequestingDocumentDateTime>
<DefaultSetID>HAERFZ</DefaultSetID>
<SoldTo>544759087</SoldTo>
<SpecialInstruction>RameshSP10RameshSP10RameshSP10RameshSP10RameshSP10RameshSP10RameshSP70RameshSP10RameshSP10RameshS100RameshS110</SpecialInstruction>
<ClaimCode>90198816</ClaimCode>
<PartialShip>Y</PartialShip>
<ReceiverAddress />
<SpecialDeliveryInstruction>RameshSP10RameshSP10RameshSP10RameshSP10RameshSP10RameshSP10RameshSP70RameshSP10RameshSP90RameshS100</SpecialDeliveryInstruction>
<OrderStatusCode>R</OrderStatusCode>
<OrderReason>
<OrderReasonCode>RSRJCT</OrderReasonCode>
<OrderReasonDescription>Info The order has been rejected by HP-RSAP</OrderReasonDescription>
</OrderReason>
<OrderReason>
<OrderReasonCode>E9850A</OrderReasonCode>
<OrderReasonDescription>Error Price is different from that in HP</OrderReasonDescription>
</OrderReason>
</POConfirmationHeader>
<POConfirmationLineItems>
<HPOrderNumber>999999999999</HPOrderNumber>
<AckDateTime>20100611T030920.000Z</AckDateTime>
<LineItemClaimCode>90198816</LineItemClaimCode>
<LineItemNumber>1</LineItemNumber>
<BuyerLineItemNumber>001</BuyerLineItemNumber>
<HPProductNumber>51645AA</HPProductNumber>
<ProductDescription>NLA - REORDER 51645BA (40)</ProductDescription>
<RequestedProductQuantity>40</RequestedProductQuantity>
<ProductQuantity>40</ProductQuantity>
<RequestedDeliveryDate>20100630</RequestedDeliveryDate>
<RequestedProductUnitPrice>167.44</RequestedProductUnitPrice>
<ProductUnitPrice>160.00</ProductUnitPrice>
<RequestedCurrencyCode>RM</RequestedCurrencyCode>
<CurrencyCode>RM</CurrencyCode>
<StdDiscPercent>30</StdDiscPercent>
<PromoDiscValue>7.44</PromoDiscValue>
<ShipModeDescription>Air</ShipModeDescription>
<LineItemStatusCode>R</LineItemStatusCode>
<LineItemReason>
<LineItemReasonCode>E9850A</LineItemReasonCode>
<LineItemReasonDescription>Error Price is different from that in HP</LineItemReasonDescription>
</LineItemReason>
</POConfirmationLineItems>
</ServiceContent>
</Document>
</B2BGatewayDoc>
Outfile we have to get:
UNA:+.? '
UNBUNOC:3SENDERRECEIVER100625:1908+1'
UNH1ORDRSP:D:97A:UN'
BGM231SP30-60659-S++RE'
DTM+242:20100525T120000.000Z:304'
FTXSIN++RameshSP10RameshSP10RameshSP10RameshSP10RameshSP10RameshSP10RameshSP70:RameshSP10RameshSP10RameshS100'
FTXACD++RSRJCT'
FTXAAO++Info The order has been rejected by HP-RSAP'
FTXACD++E9850A'
FTXAAO++Error Price is different from that in HP'
FTXDIN++RameshSP10RameshSP10RameshSP10RameshSP10RameshSP10RameshSP10RameshSP70:RameshSP10RameshSP90'
FTXACB++455'
RFF+IT:HAERFZ'
RFF+ACT:90198816'
NADST544759087:160:16'
NADBYINS:160:92'
CTAAT:YANG MINGJIN(IRENE'
COM+IRENE.YANGINGRAMMICRO-ASIA.COM:EM'
COM+021-24016684:FX'
COM+021-24016753:TE'
NADSEINS:160:92'
CTAAT:HP CO OM'
COM+GOPALKRISHNANVHP.COM:EM'
COM+65-67271815:TE'
SCC9BK'
LIN17'
PIA5001:PL'
PIA551645AA:VP'
IMDF+:::NLA - REORDER 51645BA (40)'
QTY+21:40'
QTY+113:40'
DTM+137:20100611030920:304'
DTM+2:20100630:102'
FTXTRA++Air'
FTXACD++E9850A:Error Price is different from that in HP'
PRI+INF:167.44::QTE'
CUX+3:RM:9'
PRI+INF:160::NTP'
CUX+3:RM:14'
PRI+INF:30::DPR'
PRI+INF:7.44::PRP'
RFF+ACT:90198816'
RFF+VN:999999999999'
UNS+S'
UNT411'
UNZ11'
Check it....
Thanks,
Kishore

Reg:Seeburger BIC code list file

Hello All,
I need the seeburger code-list files for the following version in EDIFACT, 0065EDIFACT_UN_D06B.cgprop and 0052EDIFACT_UN_D06B.cgprop.Please guide me.
Thanks,
Kishore

Hi,
Check the site:
wwww.seeburger.com
Regards,
Sushama

Error in Seeburger BIC Mapping

Hi all,
I am working on Seeburger BIC Mapping Designer.
As i am starting off with it, i have planned to do a very simple scenario File to file.
Source would be an XML and target also would be an xml.
Compilation is fine, but while converting I am gettuing an error
"[Error:ID=2023;LEVEL=1] InhouseDocReader readNextSegment(): offset[4(read Segment : KA\)]: caught ReadingException: Length limit exceeded - no SEG. delim. found!!!
DESCRIPTION: InhouseDocReader causes an ReadingException while trying to read the next segment of current file, abort
<<ErrorStreamEnd>>
Conversion error "
Please let me know what should be done.
Even I have enabled SetIngnoreCRLF option in the source options.
Cheers,
Karthick

Hi Karthick,
Where do you get this error?
In BICMD ?
Have you created the E2X and/or X2E mapping programs in BICMD tool?
Test it locally in the tool intself before deploying the mappings to XI server.
Follow these steps to create a 1;1 mapping for XML to EDI and EDI to XML conversion program:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948;jsessionid=(J2EE3414900)ID2060961950DB01298938248398894809End
Regards,
Ravi

Seeburger BIC let errors pass

Hi,
We have a scenario where we read from a FTP site. We are using seeburger BIC to convert the messages to something readable.
Unfortantly there are also som junk messages in the file folder or they contain a UNA that Seeburger does not understand. This mean that the seeburger module throws an error. It seems like the FTP adapter cannot move the file to the error folder, so the next file can be processed.
Any ideas on how this can be changed so we can process the files even when some of the messages are failing..
Daniel
[figaf|http://figaf.com]

Hello Daniel,
It seems like the FTP adapter cannot move the file to the error folder, so the next file can be processed.
Any ideas on how this can be changed so we can process the files even when some of the messages are failing..
It could probably be also related to the issue of the file adapter archiving e.g processing mode is set to archive and when there are errors, the rest of the messages cannot be processed or at least some a stucked. What we have done is to set the mode to delete and disable archiving for the moment. Maybe if you also disable the archiving for faulty files, it could also work on your end.
Hope this helps,
Mark

Seeburger BIC mapping error(on changing mandatory fields)

Hi Experts,
I am working on IDOC to EDIFACT file scenario with seeburger.
Earlier my end to end scenario was working fine. I got a requirement to change all the mandatory fields of segment NAD into non mandatory field. To acheive this i changed my Seeburger BIC mapping and target XSD in PI. After this process i create .sca file and ask basis to upload it.
But after deployment i am getting error in communication channel where i am using BIC mapping. The error is message is quite big, still i am attaching a part of it. Please help
Message processing failed. Cause: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: BICMapping: runMapping() FATAL ERROR: java.lang.OutOfMemoryError: Java heap space (failed to allocate 16777240 bytes) Stacktrace: java.lang.OutOfMemoryError: Java heap space (failed to allocate 16777240 bytes) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:191) at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:111) at java.io.BufferedWriter.write(BufferedWriter.java:212) at java.io.Writer.write(Writer.java:126) at com.seeburger.jucon.dochandler.util.GrammarFileWriter.write(GrammarFileWriter.java:262) at com.seeburger.jucon.dochandler.EdiSegmentData.write(EdiSegmentData.java:234) at com.seeburger.jucon.dochandler.Segment.write(Segment.java:645) at com.seeburger.jucon.dochandler.EdiSegmentData.write(EdiSegmentData.java:390) at com.seeburger.jucon.dochandler.Segment.write(Segment.java:645) at com.seeburger.jucon.dochandler.EdiDocWriter.write(EdiDocWriter.java:367) at com.seeburger.jucon.dochandler.InhouseDocWriter.flush(InhouseDocWriter.java:884) at com.seeburger.jucon.mapping.Mapping.run(Mapping.java:2429) at com.seeburger.jucon.seebicapi.BICMapping.runMapping(BICMapping.java:1724) at com.seeburger.jucon.seebicapi.BICMapping.run(BICMapping.java:2518) at com.seeburger.jucon.seebicapi.BICMapping.startSyncMapping(BICMapping.java:1415) at com.seeburger.bicxiadapter.CCIInteraction.convert(CCIInteraction.java:1201) at com.seeburger.bicxiadapter.CCIInteraction.convertCalledFromModule(CCIInteraction.java:911) at com.seeburger.bicxiadapter.CCIInteraction.execute(CCIInteraction.java:313) at com.seeburger.xi.api.cci.impl.nw71.SeeXIInteractionProxy71.execute(SeeXIInteractionProxy71.java:86) at com.seeburger.bicxiadapter.module.CallBicXIRaBean.process(CallBicXIRaBean.java:384) at com.seeburger.xi.api.module.impl.nw71.SeeModuleAdapter71.process(SeeModuleAdapter71.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal
java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:266) DESCRIPTION: BICMapping: FATAL ERROR: Internal Fault. Class could not be load or instatiated. Check Installation, access rights. Last error: java.lang.OutOfMemoryError: Java heap space (failed to allocate 16777240 bytes)
Regards,
Shradha

Hi,
Even I faced a Similar problem...
1) make sure that the size of the data that is coming to BIC map is not larger than the size defined in the Source field (Check In BIC and SAP XI/PI map.
2) Make sure id any other seeburger mapping are working fine , This is because you have to deploy the file in form of Active mapping.sca in SAP XI/PI after the changes are made on BIC side.
3) Check the Adapter Engine Cache ...
Hope this helps..
Regards,
Sainath Chutke

Seeburger BIC Mapping deployment issue in PI 7.1

Hi experts
We have upgraded from XI 3.0 to PI 7.1 and seeburger is also upgraded to a compatible version.(2.x).
Mappings_user.sda was used in 3.0 environment.
But we are not able to deploy the same in 7.1. I think sda format is not supported in 7.1.
Is there any way to convert .sda to .sca and deploy?
Or how can we generate a compatible deployment file for 7.1?
I have tried using BIC mapping designer,but it shows the option for .sda and .jar only.
Thanks in advanceDhanish Joseph

Hi
I have installed BICMD 632 version and imported .BICMD project file.
Then assigned sda/sca number to it and created deploy file.(Mapping_user00.sda).
Then installed this in PI system using JSPM.
I have tested allmost all the mappings successfully except one in PI system.(EDI 990 message).
When i send data to PI data comes to channel and it shows conversion error. But detailed information not available.
In seeburger monitoring the message goes to recovery mode.
I have used the input 990 X12 and tested in Seeburger BIC MD. And there it is success!!!!!! So i am confused what is happening when it comes to PI system.
I faced some issues>>>
1. while importing project file into BIC MD it asked for apply some autocorrection for one map.(different than this). I have clicked on cancel
2. When i assigned SDA number to my project i have selected 2.1.0 SDA version( 1.8.0 option was also there).
Your prompt reply is greatly appreciated .
Thanks

Seeburger BIC module not working

I am using Seeburger BIC module in my sender file adapter. But when I pick up an EDI file using this file adapter, the BIC module is not called. The file adapter simply passes the EDI file to Integration Engine without passing it through the BIC module. Hence, message mapping fails at Integrating Engine as the Message is not in XML form. Also I am not getting any error in adapter monitoring/Message monitoring saying that the adapter module does not exist.
The BIC module is deployed on XI server. I have activated my communication channel. I have put the module names correctly and in proper sequence and also there are no typo errors in entering the parameter names.
Please help.
Regards,
Shweta

R u passing the correct mapping name under the parameter value in module configuration?
Regards,
Anoop

Can SeeBurger BIC Mapping tool automatically remove Delimiters?

Hi all,
When we map IDOC's to EDI X12 messages using the SeeBurger BIC Mapping tool, we sometimes have delimiters occur in fields such as name or address. We are using the setDestinationDelimiter and have changed our delimiters so this occurance is rare. However the problem may still occur. This causes an invalid message to be passed to our partner.
One option is to use XI mapping and the replace function on each field however this is cumbersome and not the ideal solution.
Is there a way to automatically remove Delimiter characters from fields as part of the BIC Mapping.
Cheers,
John

Hi Satish,
Thanks for re-iterating the problem. You are absolutely right that this does cause an invalid message.
Also thanks for your suggestion regarding asking business not to enter the data, this has been done and as stated the occurences of these delimiters in the fields will be low, usually due to user error.
We still however want to cater for these occurrences and prevent an invalid message being sent to the partner.
I'm not sure if you've ever used the BIC Mapping tool and what I'm really looking for is someone with experience in this area to give a solution that works. Anyone out there who can help?
Cheers,
John

Seeburger BIC problem

Hello experts,
I'm facing a nasty Seeburger BIC problem in my receiver adapter when converting from XML to EDI.
The error is:
- SEEBURGER BICXIADAPTER.MODULE Message could not be forwarded from the Module (CallBicXIRa) to the JCA adapter.
Adapter Framework caught exception: BICMODULE:Adapter call failed. Reason:
- Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error in BICMODULE-module:Adapter call failed. Reason: .
As you can see, the reason is not mentioned.
When I look into the message monitoring, I see the message does not have a payload. On the SOAP ducument is provided with this content:
authorization:Basic UElJU1VTRVI6SUQzaW5zdGFsbA== accept-encoding:gzip
sap-xi-messageid:4BA11A89186666D8E1000000C0A8A310 content-
length:2916349 host:id3-ma-dwh1.mrco.be:51300 user-agent:SAP NetWeaver Application Server (1.0;711) content-
type:multipart/related;boundary=SAP_001E0BFD21001DEF8CBF15AFFC885B07_END;type="text/xml";start="" soapaction:"http://sap.com/xi/XI/Message/30"ApplicationMessageasynchronous4ba11a89-1866-66d8-e100-0000c0a8a3102010-
03-17T19:07:56ZID2CLNT001SteriaVANBC_UTILMDToSteriaVANMDSnapShot_In_AExactlyOnceInformationOffID2CLNT001XI4ba11a89-1866-66d8-e100-0000c0a8a3103.0is.13.id3-ma-dwh1XI4ba11a89-1866-66d8-e100-0000c0a8a3103.0af.id3.id3-ma-dwh1XIRA4ba11a89-1866-66d8-e100-0000c0a8a310MainDocumentApplication
The Seeburger modules used in my receiver adapter:
1. localejbs/CallBicXIRaBean -- BIC
2. localejbs/Seeburger/Zip -- ZIP
The Module Configuration:
BIC - destEncoding - ISO8859_1
BIC - destSourceMsg - MainDocument
BIC - destTargetMsg - MainDocument
BIC - mappingName - X2E_....
BIC - srcEncoding - ISO8859_1
ZIP - mode - zip
ZIP - sourceDest - MainDocument
ZIP - targetDest - MainDocument
ZIP - zipFormat - gzip
Messages fail at random. ABAP mapping and data are ok.
I think there is a problem with capacity or memory or something.
Anyone any idea?
Thanks a lot!
Dimitri

>
Dimitri Sannen wrote:
> Hello experts,
>
> I'm facing a nasty Seeburger BIC problem in my receiver adapter when converting from XML to EDI.
>
> The error is:
>
> - SEEBURGER BICXIADAPTER.MODULE Message could not be forwarded from the Module (CallBicXIRa) to the JCA adapter.
>
> The Seeburger modules used in my receiver adapter:
>
> 1. localejbs/CallBicXIRaBean -- BIC
> 2. localejbs/Seeburger/Zip -- ZIP
>
Dimitri,
The reason that you are getting this error is because you are missing the exit module bean. add this module after the zip module
Processing sequence
3. localejbs/ModuleProcessorExitBean Local Enterprise Bean Exit
Module configuration
exit JNDIName deployedAdapters/SeeXIAS2/Shareable/SeeXIAS2
There is an exit entry missing which actually is used to pass the bic data to PI box.
Regards,
Pavan

Seeburger BIC Help!!

We have followed all the steps for deploying Seeburger BIC module. I am currently trying to use File adapter and configure BIC module in the file adapter. I am successfully able to post IDOCS from R/3 but cannot see any errors or messages at the. If I post IDOCS without configuring BIC everything works fine (in terms of message transfer not EDI mapping).
Does anyone have an idea on why this is happening? how to debug BIC? Where I can find logs ?
Any help is greatly appreciated.

Hi,
You can folow the following steps inorder to send the IDOC into EDI
1) Find out the Correct Mapping Name in BIC mapping Designer. In order to get the Standard Mappings into your BIC tool you need to import the prj_GeneratorMappings.zip.bicmd which is found under the path
\user\bicmd\Exchange after installing the BIC map designer. This will import the Standard
Mappings that are available with the Map designer by creating a new GeneratorMappings
project tab.
2) And also we need to import another file prj_SeeburgerFormatMapping_1.7.zip.bicmd which
comes with the Seeburger EDI adapter package. Once we import this we will have all the
standard Structure for the EDI messages and standard mappings to convert the EDI Message
structure to XML and vice versa.
3)Now we need to copy all the standard mappings which ever is required from the
SeeburgerFormatMapping_1.7 project to ActiveMappings project Tab, to generate the SDA
file which needs to be deployed in XI server through SDM.
Note: This SDA file generated will always have the lastest mapping that needs to be deployed in
the server or in other words, once we generate an SDA file with selected mappings and if we
need to include few more mappings in the later stage then we have to append all those mappings
in the Active mappings directory and regenerate the SDA file.
Regards
Seshagiri

Batching different messages using Seeburger BIC

Hi Experts
I have an interesting requirement. I need to batch different messages e.g. ORDERS, ASN & Controls into a single Interchange. They are all EDIFACT messages and we are using Seeburger & BIC.
Any idea on how to do this?
regards

reject that nightmare requirement because it would be very difficult for the monitoring team to find error causes in such a message. Imagine BIC conversion will give some the infamous conversion errors because some string is too long. Now if you have dozens of messages in the same document, good luck
CSY

Seeburger EDI adapter Vs Seeburger BIC adapter

hi,
what is the difference between Seeburger EDI adapter Vs Seeburger BIC adapter.any docs please.
thank you,
babu

Hi,
Seeburger EDI adapter Vs Seeburger BIC adapter.
If your edi file converts with BIC mappers then you would have to use BIC adapter or BIC modules, i hope BIC modules, next EDI Adapters see the below links to get more details..
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards
Chilla

SAP GTS------- SAPPI with Seeburger BIC----- ATLAS using with SAP PI

Hi All,
I have scenario this SAP GTS----->SAPPI with Seeburger BIC--->ATLAS(German customs system)
1)Inbound flow: SAP GTS will send the customs declaration message to ATLAS(German customs system)
2)outbound flow: response messages from ATLAS(German customs system) approved the customs declaration message and send to SAP GTS
How to achieve using with SAP PI with Seeburger modules. What are adapter is required for this scenario.
Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send to Atlas systeam.
For mapping Source is Idoc (CCECUS02) and Target is EDIFACT(CUSDEC_UN_D96B).
Regards,
Ramesh

>
Ramesh Gulipalli wrote:
> Hi All,
>
> I have scenario this SAP GTS----->SAPPI with Seeburger BIC--->ATLAS(German customs system)
>
> 1)Inbound flow: SAP GTS will send the customs declaration message to ATLAS(German customs system)
> 2)outbound flow: response messages from ATLAS(German customs system) approved the customs declaration message and send to SAP GTS
>
> How to achieve using with SAP PI with Seeburger modules. What are adapter is required for this scenario.
>
> Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send to Atlas systeam.
>
> For mapping Source is Idoc (CCECUS02) and Target is EDIFACT(CUSDEC_UN_D96B).
>
> Regards,
> Ramesh
> .
for converting an XML to EDI or vice versa you can use the seeburger adapter.
http://www.seeburger.com/xi-pi-adapters/

Reg:Seeburger BIC Error

Similar Messages

Maybe you are looking for