BIC Mapping Error

Hi
I am getting this error when I am trying to map the EDI and XML file in the test Environment. Kindly help me on this
The error I am getting
[Error:ID=2099;LEVEL=1] InhouseDocReader doSyntaxCheck(): offset[7646]: the found segment <?XML VERSION="1.0" ENCODING="UTF-8"?>
Any Suggestions

Hi Rohan,
Its seems line 7646 might have a data issue. If you remove the data or rectify the data it should work.
With testing try maybe to test with a smaller file first and then a big one.
Regards,
Jannus Botha

Similar Messages

BIC mapping error with Text as trasnfer mode & File type

Hi guys,
I am using ftp adapter in my sender channel and also using BIC mapping in the sender side.
When i specify "Binary" as my transfer mode as well as File type, It is working fine.
When i specify "Text" as my transfer mode as well as File type, i am getting the below BIC mapping error. According to client requirement i am supposed to use Binary. Can anyone help me on this.
SEEBURGER BICXIADAPTER --- CONVERSION ERROR ---Error: [Error:ID=2023;LEVEL=1] InhouseDocReader readNextSegment(): offset[12(read Segment : BILLINGHEADER)]: caught ReadingException: only whitespaces as fill characters allowed!, Trace: [com.seeburger.jucon.dochandler.util.WrongFormatException: only whitespaces as fill characters allowed! at com.seeburger.jucon.dochandler.inhousereader.InhouseSegmentReader.readNextSegment(InhouseSegmentReader.java:384) at com.seeburger.jucon.dochandler.inhousereader.InhouseSegmentReader.readNextSegment(InhouseSegmentReader.java:193) at com.seeburger.jucon.dochandler.InhouseDocReader.readNextSegment(InhouseDocReader.java:2399) at com.seeburger.jucon.dochandler.InhouseDocReader.moveNext(InhouseDocReader.java:1818) at com.seeburger.jucon.mapping.E2X_DT_BILLINGDATA_2.main(E2X_DT_BILLINGDATA_2.java:991) at com.seeburger.jucon.mapping.Mapping.run(Mapping.java:2313) at com.seeburger.jucon.seebicapi.BICMapping.runMapping(BICMapping.java:1636) at com.seeburger.jucon.seebicapi.BICMapping.run(BICMapping.java:2386) at com.seeburger.jucon.seebicapi.BICMapping.startSyncMapping(BICMapping.java:1343) at com.seeburger.bicxiadapter.CCIInteraction.convert(CCIInteraction.java:1167) at com.seeburger.bicxiadapter.CCIInteraction.convertCalledFromModule(CCIInteraction.java:873) at com.seeburger.bicxiadapter.CCIInteraction.execute(CCIInteraction.java:294) at com.seeburger.bicxiadapter.module.CallBicXIRaBean.process(CallBicXIRaBean.java:363) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:102) at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292) at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103) at com.sap.aii.adapter.file.File2XI.send(File2XI.java:3672) at com.sap.aii.adapter.file.File2XI.processFtpList(File2XI.java:2408) at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:630) at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:513) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) ] DESCRIPTION: InhouseDocReader causes an ReadingException while trying to read the next segment of current file, abort

Hi Pratichi,
in my point of view having text as the file type,the file will be having characters that are used for Segment separators or Element separators ( like space ) in the standard EDI format message. Hence it is throwing exception in X2E mapping. It is just my point of view but not sure.
Thanks,
Shabbir.

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

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

Error in BIC mapping

Hello Pals,
Am using BIC mapping for converting a flat file to xml, am able to convert all formats of flat file but BIC mapper is throwing error if my input file has characters like ä , Ü and § . Upon removing the special characters from my input file, BIC mapper is giving the desired xml output file, If special characters are kept in input file, it throws error.
I tried to change the BIC data type for the field from A to AN, but nothing seems to be working...
Kindly help
Regards
Vijay

Hi,
Your characters looks like umlaut characters ..if yes then there is an option for handling them by specifiying the function mode setSourceUmlautMode to ON at child level mapping or at source mapping similarly at target too..
if not then you need to look for encoding which can be set with the option setXMLEncoding/SrcEncoding...options..
HTH
Rajesh

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 Mapping Designer: Special Character (German Umlaut) Problem

Hi,
i have created a Mapping with Seeburger Mapping Designer (Invoicd96a to XML). I started the test environment, compiled the mapping and converted the Message to XML. I got a syntax error in the destination file so i added the setSourceEncoding("UTF-8") option and i got a working xml file.
My problem is that all special characters, will be displayed as ? So the word "Beträge" will be converted to "Betr?ge".
What i have to di, to fix this problem ?
Thanks in advance
Matthias

hi,
i have to create an Edifact to XML Mapping with the BIC Mapping Designer. After creation i can deploy this mapping to SAP XI and calling it by using it as module in the specified adapter.
My idea is that the mapping should working correct in test enviroment before i deploy to SAP PI.
Perhaps anyone has an idea.
regards
Matthias
P.S.: A few month ago i had a similar problem with the conversion agent and it was just a "secret" checkbox

Problem in SEEBURGE BIC mapping adapter

Hi experts
I am using SEEBURGER MAPPING adapter for file to idoc scenario .I have to convert an input flat file into xml using BIC mapping adapter.The problem is that when i am giving input file to convert into xml ,the conversion is failing with a error that a special character(?) occurs in the begining of file.when we r opening the file then we r not able to see any special character.The file is in UTF16 Little endian encoding. we r unable to find that how the spechial character is coming in the input files and how to debugg it.Plz guide me how to proceed.Is there any function in SEEBURGER to remove special character from the source file?
Regards
Neha

Hi Neha,
Seeburger is providing Modules (Configurable in CC module chain) described in SAPXI_SeeXIModules_en.pdf with additional functionality like Replace String,Start Local Up, Charset Conversion, zip and dynamic Configuration.
So if you have those modules installed you can use Replace String functionality to replace this string.
Regards
Naycho

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

Mapping error in PI 7.1

Hi All,
When i am trying to create a new mapping or coyping the existing mapping(which is already activated) , i am not able to activate the mapping . I am getting the following error :
Source text of object Message Mapping: new |
urn:abc:MessageOut has syntax errors: Source code has syntax error:
Source strcuture and everything is perfect as i had created previous mapping using the same source structure.
Please advice as to what might be the issue here and what is the solution.
Regards
Vinay P.

In each and every mapping which is already avialble in IR and the new ones that i am trying to create ...i am getting the followin exception throughout if press F7 in the mapping ...as a result u cant actiavte any changes in the existing mapping nor in the new mapping
Error:
Source text of object Message Mapping:
Mapping name| urn:abc:namespace:SI_Interface has syntax errors: Source code has syntax error:
Regards
Vinay P.

Strange Data Mapping Errors after SEM 6 Upgrade. Please assist.

Hi All, I encountered these sudden Mapping errors after I tried to do Testing in Post Upgrade Sand Box. Here I am trying to to perform Collected Reported Financial Data under Data Collection Method for a particular Company Code 3040. Kindly help me with some quick responses as this is kind of high priority. The errors and the Diagnosis Notes I am unable to follow as I do not where I shall write those Mapping Rules they are referring to. I do not even know if that need to apply any SAP Notes as such. Once again Highly appreciate your quick response and Many Thanks in Advance.
Regards, BIP
Input conversion for field Period Value LC has invalid format Message no. UCT8210 Diagnosis The mapping rule for target field Period Value LC contains a move with a selected Input Conversion indicator. Therefore, the system performs an input conversion prior to creating the target data. However, an error in the input conversion occurred while moving the source key figure to the target key figure Period Value LC. This means that the format used for the input conversion is incompatible with the target data. System Response The system will not perform the move. Procedure Examine the mapping rule for field Period Value LC. Either select the Conversion Exit indicator or deselect the Input Conversion indicator. Execute the method again. -
3040 is incompatible with input format for field /1FB/COMPANY Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field /1FB/COMPANY from the mapping rule for the target field. 3040 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field /1FB/COMPANY. However, the value 3040 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 3040 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field /1FB/COMPANY. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field /1FB/COMPANY. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field /1FB/COMPANY. If incorrect values were selected, make sure that the mapping rule used by source field /1FB/COMPANY has been defined correctly. If the mapping rule is correct and value (3040) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 3040 for field /1FB/COMPANY and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field /1FB/COMPANY, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field /1FB/COMPANY is unsatisfactory: You can define a source selection for field /1FB/COMPANY in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field /1FB/COMPANY. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule. -
Cannot derive the source selection from target field Version Message no. UCT8252 Diagnosis Field Version has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Version. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Version. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Versionthrough mapping), choose one of the alternatives below: Change the mapping rule for field Version so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Version. -
Cannot derive the source selection from target field Group Currency Message no. UCT8252 Diagnosis Field Group Currency has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Group Currency. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Group Currency. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Group Currency through mapping), choose one of the alternatives below: Change the mapping rule for field Group Currency so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Group Currency
1 is incompatible with input format for field FISCPERIOD Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field FISCPERIOD from the mapping rule for the target field. 1 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field FISCPERIOD. However, the value 1 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 1 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field FISCPERIOD. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field FISCPERIOD. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field FISCPERIOD. If incorrect values were selected, make sure that the mapping rule used by source field FISCPERIOD has been defined correctly. If the mapping rule is correct and value (1) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 1 for field FISCPERIOD and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field FISCPERIOD, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field FISCPERIOD is unsatisfactory: You can define a source selection for field FISCPERIOD in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field FISCPERIOD. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule
Input must be in the format ___,___,__~ Message no. 00088 Diagnosis Your entry does not match the specified input format. System Response The entry in this field was rejected. Procedure The entry must comply with the edit format. The following edit format characters have a special meaning: "_" (underscore) There should be an input character at this point; this should be a number for numeric fields. "." (decimal point) (applies to numeric fields) The decimal point occurs here (setting in the user master record). "," (thousands separator) (applies to numeric fields) This separator occurs (optionally) for more than three figures. Depending on the setting in the user master record, it can be a period or a comma. "V" (applies to numeric fields) The operational sign appears here. If used, it must by at the right margin of the field. The sign is either "-" or " "(space). "~" (tilde) (applies to numeric fields) As of and including this character, leading zeros must also be entered. Otherwise, this character has the same meaning as an underscore. Leading zeros need not be entered on the left of the tilde. They are not output at this position. All other characters have their normal meanings and must be entered in the same position as in the edit format.

Hi Dan,
Could you Kiindly advise me where we need to write the Mapping Rules in Consolidation Monitor? All he time the errors refering to Mapping Rules. The only Tab I seen "Mapping" is in Data Basis But as per my Understanding Iwe do not have much to do there as it is system generated Mapping Tab.
Where we actually go and select/deselct those Input Conversion Indicator/ Conversion exit Indicator.
Highly appreciate your advise.
Thanks and Regards,
BIP

Java.util.EmptyStackException Mapping error

Hi All,
I am integrating SAP ECC 6.0 system with SAP SNC.
For these i am using standard content of SAP SNC
I am getting following mapping error :
TransformerConfigurationException occurred when loading XSLT InvoiceRequest_InvoicInvoic01_01.xsl; details: Could not load stylesheet.com.sap.engine.lib.xml.util.NestedException: Error parsing query. -> java.util.EmptyStackException
Plz help me out
Regards Milan

hi,
check the interaface mapping which is used in your flow
inside integration repository - is it working over there?
do you see the XSL file in the external archives in repository?
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Multi-Mapping Error after copying into new namespace

Hi everybody,
we got a BPM running using a multi-mapping.
We decided to design new namespaces. After copying every IR object (datatype, message-type, mappings etc.) --> SXMB_MONI shows a mapping-error.
But when I take the payload and test the mapping, everything is fine?
Any ideas?
Regards Mario

Hi,
If your payload has Messages tab remove that..and test the payload.
Payload doesn't have any Messages tab.
Just i have given example payload..this payload two strucures it will split into twofiles..and compare your payload should be like same
<?xml version="1.0" encoding="UTF-8"?>
<STRUCTURE>
<EMP_DETAILS>
   <EMPNO>123<EMPNO>
   <EMPNAME>XYZ<EMPNAME>
<EMP_DETAILS>
<STUDENT_DET>
   <STUO>123<STUNO>
   <STUNAME>XYZ<STUNAME>
</STUDENT_DET>
<STRUCTURE>
Regards,
Venu.

Catch Mapping Error in File to IDoc scenario

Configured BPM and now learning Error Handling. I know that through BPM we can handle system Errors, but I doubt whether Mapping error is a system error.
I am interested to know the classification of errors with examples, preferably listing out all types of errors.
Please provide some weblogs or explain briefly how to handle system and application errors through BPM.
Thanks,
Raja

Hi Raja,
You will need CCMS if you want to send the Alerts to external system or you want to access the ALerts from the transaction. You can capture your alerts without this also.
When you go to Alert Configuration in the Runtime Workbench you can see Create Alert Rules. These rules are pertaining to the error generated in your AF,AE or IE.
Once you have completed the whole config. The error happening in the AE, IE or AF would trigger the alert. you can see this in your Alert Inbox.
The best would be if you go through the URL I have mentioned below.
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
You have to use BPM only if you want to do an activity after the alerts are raised.
Regards
Vijaya
Message was edited by: vijaya kumari

Mapping Error in XI Configuration for MM-SUS Scenario

Dear Experts,
I am working on MM-SUS Classic Scenario,
We have done all basic setting in SRM, ECC and SUS.
Now we are configuring XI Scenario(Working on ESOA Architecture), while configuring XI Scenario, I follow the mention steps :
I have started from Integration Builder in XI (using T-code SXMB_IFR)
1. I have assigned two Business System( for ECC and SUS) In integration Builder (Creates Communication Channels Automatically) .
2. Modify IDOC and XI Communication in ERP and SUS Business system respectively.
3. Now select Tools -> Transer Integration Scenario from Inegration Repository and Create Scenario in it properly
(Included Assign Services, Configure Connections, Generate etc).
4. In last, save scenario.
After configuration XI I am not getting Scenario Data (Objects and Configuration Overview data) in it.
When i click to Check Configurability under Model Configurator of mine Scenario, I found following Errors ( I am Mentioning only some errors) :
Component View SE_Services_Procurement: Connection from Send Z_CREMAS_SUSMM to Business Partner empfangen has no mapping
Component View SE_Services_Procurement: Connection from Send_PO_From_MM to Receive_Purchase_Order has no mapping
Component View SE_Services_Procurement: Connection from ServiceAcknowledgementConfirmationRequest to ServiceAcknowledgementConfirmationCreate has no mapping
Component View SE_Services_Procurement: Connection from InvoiceRequest senden to Receive INVOIC has no mapping
Kindly correct me if am missing some, and help me out, what should have been done to remove this mapping errors.
Thanks in advance,
Regards,
Pawan Keshwani

If you are on >= SP9 you do not need to perform that action at all.
Go to SU01 transaction assign SAP_XI_DEVELOPER role for the desired users and try it.
regards
Shravan

BIC Mapping Error

Similar Messages

Maybe you are looking for