BDBG IDOC with heirarchy

hi all,
i have a really wierd problem...
i am creating a idoc using BDBG... i am trying to create the IDOC with a header and detail heirarchy...
i searched a bit and found BDBP for the heirarchy configuration.
the IDOC type should seem like this:
header
|
> detail
but it seem that BDBP has not effect and the IDOC type seem like this:
header
detail
i am trying to create the heirarchy so that the mapping in XI should be easier.
could you help me please?
what am i missing?
btw,
the method function interface look like this:
TABLES
   IT_HEADER
   IT_DETAIL
   ET_RETURN
regards,
Roi Grosfeld
Edited by: Roi Grossfeld on Nov 4, 2008 10:00 AM

hi Gaurav,
this won't work as the structure of the idoc in the SAP system is different from what you suggest.
so the SAP system won't recognize the heirarchy which i define the XSD.
i want to change the heirarchy in the SAP System and when i import it to the PI i will have it and i won't need to do any changes to the XSD.
Regards,
Roi Grosfeld

Similar Messages

IDOC for CHRMAS04 with Heirarchy Values??

Hi All,
Hoping someone has experience in defining a IDOC for Basic Type CHRMAS04 with Heirarchy values. Also how do I manually create one using transaction CT04.
Basically we want the characteristic values to look as follows
Parent 1
Parent 2
Parent 3
Child 1 Linked to Parent 1
Child 2 Linked to Parent 1
Child 3 Linked to Parent 1
Child 4 Linked to Parent 2
Child 5 Linked to Parent 2
Child 6 Linked to Parent 3
This gives a drop down list in the characteristic display.
I think field CAWN-ATWHI is the field that states this is a Parent value amd field cawn-ATZHH poins from the child to the parent.
Thanks for the Help.

The standard characteristic IDOC has all the fields required, but the definitions that come with Best Practice for Data Migration need to be modified to include these fields.
The additional fields are as follows:
Hierarchy
Counter
Parent Counter
Value High
The rules need to be as follows:
Set Hierarchy = 'X' for each value which begins a level in the Hierarchty
Set counter as a sequential value for the characteristic
Set Parent Counter as the reference to the childs parent counter
Set Value High as the reference to the childs parent value
See Example Below
NameValueValid-From DateOperator Signs GreaterLanguageHierarchyCounterParent CounterValue High
ZPM_R_WORK_CATEGORY0119000101~ENX1~
ZPM_R_WORK_CATEGORY0619000101~ENX32~
ZPM_R_WORK_CATEGORY0719000101~ENX52~
ZPM_R_WORK_CATEGORY0819000101~ENX70~
ZPM_R_WORK_CATEGORY0919000101~ENX75~
ZPM_R_WORK_CATEGORY010219000101~ENX21~01
ZPM_R_WORK_CATEGORY010319000101~ENX111~01
ZPM_R_WORK_CATEGORY010419000101~ENX171~01
ZPM_R_WORK_CATEGORY010519000101~ENX231~01
ZPM_R_WORK_CATEGORY013019000101~EN261~01
ZPM_R_WORK_CATEGORY013119000101~EN271~01
ZPM_R_WORK_CATEGORY013219000101~EN281~01
ZPM_R_WORK_CATEGORY013319000101~EN291~01
ZPM_R_WORK_CATEGORY013619000101~EN301~01
ZPM_R_WORK_CATEGORY013719000101~EN311~01
ZPM_R_WORK_CATEGORY064019000101~EN3332~06

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

Creation of Custom IDoc with Message control for sales Order

Hi all,
I am trying to create custom Outbound IDoc with message control.
I wrote the code in a function module and i want to register that function module. (as in inbound registration of function module as in BD51).I am not knowing if that registration is necessary for outbound Idoc, if so in which transacition?
Please list me the steps to create a custom IDoc for Message control.
Thanks in advance,
Regards,
John.

Hi,
You need to use FM : MASTER_IDOC_DISTRIBUTE to create outbound idoc.fill the data in the tables EDIDC,EDIDD and generate the IDOC.
check this link:
Re: Master_IDoc_Distribute
and use transaction : WEDI for IDOC configurations.
here you will have all the transactions(step by step) to set the outbound IDOC configurations.
Regards
Appana

Creation of IDOC with message type INVOIC01

Hi All,
I am trying to create a new IDOC with message type INVOIC01.
When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
The client wants me to create IDOCs with basic type INVOIC01.
Can anyone please help?
Thanks in advance.
regards
Nagarajan

Hi Nagaraj!
I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
Thank You,
Natalija

Loading Invoice XML IDoc with digital signature via XI into R/3

Hi,
I received an Invoice XML IDoc with digital signature via Mail (for test purposes) and want to load it via XI into an R/3 systeme.
My idea is to load the Invoice XML IDoc file via the File Sender Adapter into XI and send it to the R/3 system via the IDoc Inbound adapter.
Due to the digital signature the file looks like this:
0 S      *H÷
   D0 @   1 0       +      0 '      *H÷
      0 0 û      etc.
When I load the file like this with the File Sender Adapter, an error message occurs in the XI Monitoring as the XML Parser cannot read the file due to the digital signatur (as expected).
Has anybody an idea how I can configure the File Sender Adapter Communication Channel to be able to load only the XML IDoc and ignore the digital Signature strings?
Thanks in advance for your support.
Alex

BTW
do use the second way you need:
Security Settings for the Sender Mail Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/27/c0524257a1b56be10000000a155106/content.htm
and
Key Storage Service
http://help.sap.com/saphelp_webas630/helpdata/DE/e9/a1dd44d2c83c43afb5ec8a4292f3e0/content.htm
apart from adapter module config
Regards,
michal

Status 56 - IDOC with errors added

Hi everyone,
 I was configuring File to IDOC Scenario, in the receiving R/3 system, i am getting error as Status 56 - IDOC with errors added "EDI: Partner Profile not available".
 but i had already created Partner profile in WE20.
Regards,
Varun Reddy.K

Hi Varun,
 The below link will help u in solving u r problem
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Just try follow the steps followed in above mentioned link
And also check u r RFC connection in TC "SM59".
Reward with ponits if helpful
Regards
Sai Ganesh

Error in Receiver - IDoc with errors added

Hi All,
I am getting error in 56 - IDoc with errors added in receiver System.
I am new in Idoc - please tell me How to resolve this issue..
Thanks in advance..

Hi all thanks for reply .
All are the help full answer ,
I use T-code WE19 and change partner profile and execute now it is fine.
But i have checked all configuration regard partner profile from T-code WE20 it looking everything is fine but in Test tool for Idoc Processing by t-code WE19 i have checked it will taken wrong partner profile detail after giving correct manually now it is working fine.

How to generate PAYEXT (PEXR2002) IDOC with many invoices for same vendor

Hello,
We are implementing the IDOC payment processing through transaction F110. The first test we ran using multiple items for the same vendor created an IDOC with multiple E1IDPU1 segments for each invoice. We then configured a second bank and ran the test again. This time the multiple invoices for the same vendor generated a seperate IDOC.
Does anyone know where I should start looking to figure out what I did wrong? We are hoping to generate 1 IDOC for all invoices for the same vendor.
Thanks,
Brian

Hello,
May I know how or what are the steps you did to create multiple invoices and generate multiple idocs for the same vendor? I have a requirement to generate multiple payext idoc for a single vendor.
Please advise. Thank you very much!

FM to fill outbound IDOC with change document details.

Hi ,
I am working on an enhancement EXIT_SAPLMGMU_001 for an interface to track the changes to the material master.
Can someone please let me know if there is a FM to populate outbound IDOC with change document details like when a material is
created /changed. Thanks much.
Regards,
Sanjeev
Edited by: sanjeev.s on Apr 14, 2010 3:32 PM

Call the function module "MASTER_IDOC_DISTRIBUTE" to create idoc. Use function module "CHANGEDOCUMENT_READ_HEADERS" to get the change document details.
Regards
Vinod

Vendor Master Creation through IDoc with Multiple Company Codes

I am trying to create vendor masters sent from a 3rd party into SAP using CREMAS05 IDoc. I have the requirement that the vendor should be created in each of 3 company codes and the vendor number is internally assigned in SAP.
I create my IDoc with the general data E1LFA1M and multiple E1LFB1M & E1LFB5M Children. When I post the IDoc using IDOC_INPUT_CREMAS which uses Call Transaction, the vendor gets created for the first company code, but the IDoc errors on the vendor extension XK01 for the next company code with the error: "Fill all required fields SAPMF02K 0111 ADDR1_DATA-NAME1".
In debugging through this, it appears that the vendor number that gets created in the first XK01 transaction does not get passed into the data for the second XK01 call and SAP tries to create a new vendor instead of extending the newly created one.
If I force the value in during debug after the initial call transaction into the variable h_lifnr, it works fine (Vendor created with multiple company codes.
Any help would be greatly appreciated.
-Larry

I cannot give you exact solution, but can guess why this is happening, below is what I believe.
I think Synchronous update is not happening in call transaction, second transaction is getting processed before the first one is saved, debugging it works fine, because we give system enough time to save while processing.
Generally in call transaction we have MODE, if we pass S - then synchronous update happens, in your case, you need to find the way to incorporate this.
Hope it helps.
Regards,
Ravi Kishore.

MATMAS idoc with classification details - reg

Hi,
I am working in a project related to the transfer of Material Master from one system to another ( Both are R/3 systems).
I am currently using the message type MATMAS with basic type MATMAS05. With the above message type i am able to generate an idoc from source system with all of the details except for the classification details.
For classification i have configured the message type CLFMAS and CHRMAS, in the CLFMAS i am able to successfully generate an idoc with BD91/BD92 tcodes. But when the idoc is generated, the idoc gives the list of charactersistics managed in the class at each segment level but not able to retrieve the values maintained by me during the material master creation. In order the target values for each of the characteristics in the class is empty.
Please clarify me with the following queries:-
a) Is that really required to push both CLFMAS and CHRMAS for a material master classification related field values ?
b) How to get the characteristics values maintained in the material master at the idoc level ?
c) How to link the CLFMAS generated idoc and the MATMAS idoc to link the relationship?
Thanks for the understanding.
Thanks and Regards,

Classification of a material has to be send with CLFMAS IDOC separate from the material.
Usually you first distribute all characteristics and classes, then the materials, finally the classification.
You have to enter the new material number in segment E1OCLFM field OBJEK of your classification Idoc.

Error in idoc with status 20 "Error triggering EDI Subsystem"

Dear All,
I have query related to IDOC Status 20.
I am tirggering IDOC with standard t-code from IS-Retail system. I have created two ports a) TRFC port and b)File port .
We are having sending and receiveing application on two different OS i.e one XI on Windows and IS Retail on AIX(Unix). I am not able to send idoc to another system. I am getting these IDOC status in WE05 (STATUS 01 , 30 , 03 , 20 )
Keeping the above fatcs in mind could you please tell me how to remove the error with status 20 "Error triggering EDI Subsystem".

Hi prabhat,
You should have checked the automatic triggering possible at the file port level and the partner profile setting could be 'start subsytem'.
Go to WE21 and do the access test for the file port.
Once you done and find no issues then go to SM59 and test the connection for the RFC destination assigned to the ports.Possibly it has to do with the RFC destination.
Other reasons could be yours is a test client and got refreshed recently.so the production client settings might be causing this error.Check with your basis to get it working.
other reason could be the logical system assigned to the client should be having production client's name.
Check these.
I am sure you should be able to solve this issue.
Thank you.
regards,
karun.M

5 IDOC with status 29 Error in ALE service

hi there,
im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
IDOC Status Outbox:
IDOC failure between 13/07/2008 to 14/07/2009
1 IDOC with status 02 Error passing data to port
5 IDOC with status 29 Error in ALE service
IDOC Status InBox:
88 IDOC with status 51 Application document not posted
regards
raju

Hi,
Check this thread.
DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Regards.

BDBG IDOC with heirarchy

Similar Messages

Maybe you are looking for