Idoc not showing in R/3

Hi,
Iam Currentl running File to Idoc interface. Message is success in moni also and runtime workbecnh also. But when iam checking R/3 using WE19 tcode by giving date its not showing . It showing like no values found. Can anybody tel me what is the reason?

Hi,
Dont seach with IDOC no in R/3. Check in WE02 transaction not WE19
Search by Date only ........then go under your INBOUND IDOC type node in WE02 in ECC. Also Please check the ECC client no you are posting the IDOC.
Please be confirm in SLD your ECC business system client . And search the IDOC in ECC in same client no.
You can also chek in ID check Adapter Specific Message attributes for ECC business system & also click the Compare with SLD Option.
You can found this option after opening Business system in ID from menu.

Similar Messages

Need immediate help: Idocs not showing up in productive PI

Hi gurus,
we are trying to go productive today with our pi 7.0 server. now we are facing the problem, that the idocs from our productive system don't get into the pi. in the productive erp system we can see them leaving with green status, but in sxmb_moni they don't show up. can anyone please help?
regards,
michael

hi michael
tRFC calls which transfer IDocs use the function module IDOC_INBOUND_ASYNCHRONOUS at reception
If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.
To check the status of the tRFC calls, choose
Tools -> IDoc Interface/ALE-> Administration -> Monitoring->ｮ Troubleshooting -> RFC Queue (SM58) and specify any additional selection criteria.
basically The program RSARFCEX restarts unsuccessful tRFC calls.
regards
kummari

Idoc status 03 in SAP but in XI idoc not showing

Hi Experts,
in my SAP to file scenario, idoc is created successfully with status 03, but idoc is not coming to PI.
It is not happening always. some times, idocs are missing. But not able to find any error in PI.
Please guide me how to get the missed idoc.
Thanks,
Swapnashree

this is old interface and it only gave issue this time. In ECC side, when I checked, out of 4 idocs one idoc is with 03 status and other three were with 39 status.
But all in green status. No error.
RFC destination and all are correct.
Actually I am not able to see the complete error text in TRFC . that message class is not maintained. Our functional team informed that they added XX text and re import idoc and it worked. Please suggest.

Metadata values not showing in Site Studio layout using Idoc Script

Hi All,
We have a SS layout (secondary) with replaceable regions for showing content that is listed in a primary page dynamic list.
Part of the layout shows contribution elements of Contributor Data File content items, but part of layout also shows metadata values. We use  to show the content item Title with no problems.
However, for some content items, some metadata values are not showing on the layout - specifically a custom metadata field called xFinishDate (which is of type 'Date' in Config Man). The code  simply does not work (nothing is displayed) for some content items, despite definitely having a set FinishDate value. Some other content items show this value fine.
The  value works for ALL items, but the  does not, and there appears to be no difference between the items that it does, and does not work for. They are all CDF, same DocType, same CheckIn profile, etc.
The non-working items are all released and indexed. Their Content Information in Content Server shows complete metadata. I have resubmitted the non-working items for reconversion in Repo Man but no luck.
Is there something I am missing? Any help is greatly appreciated.
Luke.

Actually the default DOC_INFO resultset that is on the page seems to be for the content item being loaded into the secondary layout's replaceable regions. This is why DOC_INFO.dDocTitle gives the results expected.
However, I think I have discovered why the xFinishDate value was not showing. Using sapan's code (and modifying it a bit) I was able to print out all the metadata field names and values for default DOC_INFO resultset.
Using this URL as an example: http://www.bond.edu.au/about-bond/jobs-at-bond/BD3_011217
At the top of page region (replaceable) where the Contributor Data File is loaded into, the DOC_INFO resultset is relevant to the content item that is being loaded into the layout (content ID: BD3_011217 - as per the URL format), which is what we want.
However, throughout the Contributor Data File content, if a link is made using the Site Studio link wizard via FCK Editor (in the above case, it is the position description link, which is a link to a PDF) and the link is 'Link to a file' and the 'Choose Target section' is selected as 'Use default website section metadata', the resulting link looks like "http://www.bond.edu.au/about-bond/jobs-at-bond/BD3_011216". Any references to the DOC_INFO resultset on the page after the instance of this link now use the metadata of the content item referred to in the link, not the original content item. I have dumped out the DOC_INFO fields/values in different parts of the layout to prove this. The linked content item has no xFinishDate value so this is why nothing displays (displaying xFinishDate needs to happen after the link to the position description).
I guess I need to either:
- change the way the link is made to the content item to "Link to the Content Item's URL", but I would prefer not to expose the resulting path e.g. "[!--$HttpRelativeWebRoot--]groups/group-name/@account-name/documents/content-type/content-id.pdf"
- explicitly make a resultset using  with the content ID I know I want and use it instead of the default DOC_INFO one. Is there any other way to make a resultset comprising of a single item's metadata?
9.45 SS_GET_SEARCH_RESULTS
■ Description: This is a wrapper around the regular CS GET_SEARCH_RESULTS
service. It allows some Site Studio features to be specified simply as flags and have
the real query syntax be constructed on the server. It can modify the standard
'SearchResults' resultset to contain an additional column called 'ssUrl' which will
contain the Site Studio-friendly url for all of the search results.
■ Parameters:
– siteId: the unique identifier of the site (required).
– ssLimitScope: True/False, restricting scope to within the site only (optional).
– ssUserSearchText: user-supplied search text (optional).
– ssWebsiteObjectType: object type (optional).
– computeFriendlyUrls: True/False, modify results to include ssUrl (optional).
■ Returns: resultset named ’Search Results’.
■ Security: The user must have at write access to at least one security group on the
content server
Thanks to everyone for their help. Almost there!
Edited by: lukeb2112 on 18/01/2010 17:30

Idoc Not received on MII Message Listener

Hi All,
I am trying to post Idoc from R/3 to MII Server , but some how I am not getting it
I have configured Destination, Parter, Partner Profile on the R/3 and Message Listener on MII.
When I am trying to send Idoc from R/3 using BD10 transaction (Idoc type MATMAS), Idoc Status as 03 in WE02 transaction , but I the MII server does not show up for this.
Even the Failed Messages is showing no results.
Am I missing some thing here.
Any help is appreciated.
Kind Regards

I got the issue,
The problem was Partner was wrongly selected.
Thanks

IDOC not receiving in XI

Hi -
Using PI 7.0 and checked all the configurations and read all the related blogs but i don't see the IDOC coming into XI.
Checked the SM58 on R3 and does not show any errors.
I checked the WE02 on XI system and shows a status of 60 and 56. Status 60 says "Basic Type MATMAS05 does not exist" which is true because it does not exist on the XI system but exists on the r3 system.
All the ports on xi and r3 system seem to be fine. i pushed the idoc and shows a status '03' on the r3 side.
Any tips/ideas to solve the issue are greatly appreciated.
Thanks,
Tirumal

Hi,
Go to SMQ2 and try to check the Queue Status .
Did you check this SAP note I referred earlier- 940313
Also -http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
GO thru each step ..because it will help you to resolve the problem.
Hints-
1) check WE02 and check the status of Idoc in the R/3 system. Is it sent to XI box/port correctly ?check its control record info , in WE19
2) Did you check Partner Profiles - for outbound parameters -check out this
3) Check the SM59 entry in SAP system - pointing to XI box.
4) Check IDX5 transaction in XI box, if eevrything is success in R/3 system
5) check the Business system in XI - is it pointing to correct R/3 system.
Hope this helps,
Regards,
Moorthy

IDOC not displayed in WE05

Hi Experts,
I have successfully run my scenario CSV-pi-Idoc yesterday. IN MOni XML file is Ok. In R/3side (WE05) Idoc generated successfully. But Yesterday night Basis people change R/3 password. Now my problem is in R/3 IDOC not displayed in WE02.
Iam also change password in SM59. But no result. Where can I do changes. can any one help me.
Thanks
Hari

Hi Hari,
Make sure in SXMB_MONI in your PI system the message is showing successful flag in outbound side (ie.. drag the scroll bar to ur right had side and see if you can see checkered flag). If you see any error then go to tcode sm58 (trfc queue) and filter based on dates and u will find error logs in detail and take appropriate action.
Mostly it might be authetication problem so better to check in ur R/3 destination in Sm59 in PI system if your rfc test and authentication test is successfully showing green or not.
Thanks,
Prasanthi.

Inbound idoc not displayed in WE02

Hello All,
I have two different sending and receiving SAP system for IDocs. I am trying to learn ALE scenario. For this purpose, I created everything on my own on the sending system viz. idoc segments, idoc type, message type, rfc destination, port, logical system, ALE distribution model & partner profile and a Z program containing the function module MASTER_IDOC_DISTRIBUTE.
When I run the program on the sending side, the idoc is generated with status is 03 (data passed to port).
I am not sure what settings do I need to make it on receiving system. I created the logical system, partner profile, Z function module for inbound processing, registering of the function module & inbound process code & registered it in partner profile for the inbound message type
Please help me know, how to determine this IDoc on receiving side. In WE02, it does not show the IDoc generated by the sending system.
Thanks & Regards,
Saurabh Buksh

Hi,
You said you have used MASTER_IDOC_DISTRIBUTE. I hope you are doing a COMMIT WORK after calling this function. Reason is that this function doesn't do the COMMIT WORK and thus explicit commit work is required after the call.
regards,
Advait

Idocs not coming to XI

Hi,
In our landscape developers are trying to send Idoc from R/3 to XI system.
We have created RFC_XI as RFC connection, which they are using to trigger IDoc from R/3 to XI. Now IDocs are getting triggered from R/3 without any error, but they are not coming to XI.
Now when I checked Inbound queues in XI and found that all queues start with XBTI* are stuck with SYSFAIL error.
Through SXMB_ADM I have tried to register and activate queue for XBTI* but it gives error as below:
Error while activating queue XBTI*
Message no. XMS_ADM610
Can anyone help me regarding this so that IDocs can be processes between these systems.
How can we see wats the issue while activating Queues?
Is there anything else needs to be configured between these two systems?
Thanks & Regards,
Manish

Hi,
First of all thanks for so quick reply.
I have checked at XI Side:
In IDX2 in loaded meta data, two types of Idocs are showing
ORDERS02 and CREMAS01
In IDX1, Partner port and RFC have been configured.
at R/3 side:
RFC is checked its working fine.
Using WE20 and WE21, Partner profile and port been configured already.
In SMQS below is the status:
<R/3 Client> RFC_XI R 10 60 INACTIVE 0 <R/3 HOST NAME>
Register the destination in QOUT scheduler (SMQS) and make it as active
Destination is there (as per above) I hope entries are correct but its showing INACTIVE. How to activate it?
Select the queue from WEOUTQUEUE transaction and start the queue processing; now you can see that your XI starts receiving the Idocs
In WEOUTQUEUE when trying to see IDocs using Reciever Port as RFC_XI its showing nothing.
While I checked sent IDoc status using WE05, previously it was taking port as RFC_XI for sent IDoc but now its taking port SAPID6 after I defined port in XI for R/3 using IDX1.
For SYSFAIL Status, further message is as below:
XI restart in qRFC not allowed
Any more ideas or help? Will appreciate if anything step wise can be refer to check and rectify this error.
Thanks & Regards
Manish

PO created in SRM not showing in ERP

Dear All;
We are using SRM7, classic scenario.
The buyer converted a SC to PO then deleted it in ERP.
The SC appeared again in SoCo
He created another PO but it did not get transfeered to ERP.
In Related document of the SC, it shows the Deleted PO with status Deleted but it did not show the new one.
The SC is NOT shoiwng in SoCo anymore
In BBP_PD (document display) I can see the new PO number.
My questions:
1. How to update the staus of the SC?
2.How to transfer the PO to the backend
for your information, i executed BBP_GET_STATUS_2 but still not updated. I also checked WE05 (IDoc)
Thanks

Check the Log in RZ20 for PO.

All items of delivery is not showing on SNC Web Portal

Hi Experts,
We are facing one strange issue in SNC. I am explaining scenarion in detail.
We have one sales order having 10 line items in R/3 & it is showing correctly on SNC web portal. For that sales order we have delivery with 10 line items ( out of 10 items 4 items having Batch mentioned in delivery) in R/3 but in SNC Web Portal it is showing only 6 Items. Basically whatever the Items having batch is not showing on SNC Web Portal.
I have checked lots of deliveries & all are having same issue. I have checked all the IDOCs, XML messages to XI & then APO having all the line Items of delivery but all items are not showing on SNC Web Portal.
Could you please advice, what it this issue & how can we resolve it?
Thanks in Advance.....
Regards
Sujay

Hi Chandrasekhar,
I checked this note but this doesnot answers my query.
Regards
SV

"Users " Form Name from "User Definied Field Definition" does not showing

Hi everyone!
I start to implement the new SAP Connector on OIM 9.1.0 and one of steps is configure the lookup Lookup.SAP.HRMS.AttributeMapping.
I need to add more fields beyond those already exists, and in accord to Documentation, I need to create the UDF of these fields, but when I search of "Users" form name form "User Definied Field Definition" option, I receive the follow response:
"Query Failed: No Record For this Query"
Thinking about it, I think that necessary create one User Form, but...this form isn't a standard form?
What I do in scenarios like this?

Can you share your environment details. Are you trying it out in a newly installed OIM ?_
Yes, it's a newer fresh installation of OIM 9.10. We use the old version (9.03) in production environment and would like to upgrade to 9.10. This issue occur in a fresh installation in Development Environment.
The one possible reason for this may be due an improper upgrade to 910X. I actually faced this issue while I was installing/upgrading my OIM. I did the process all over again and it was just perfect. I am not sure that this might be an issue with you or not. But there is simply no othe reason for the Users from not showing uo in the "User Definied Field Definition"._
If you have taken a fresh backup of the schema just after installation, then import that backup dump and see if you are able to view the Users form. If in case you are not able to view it then your installation / upgrade is corrupt._
No, we don´t have a fresh dump of environment. We just follow the documentation and all the steps was done without problem. The SAP connector import the fields from the reconciliation using flat IDOC file, just only the standard fields. We need to add newer fields and attributes and after, we face this problem.

Idoc not getting posted

Hi All,
We are posting the Business partner data from HR to CRM through Idocs. Though we are able to get almost all the Business Partners in CRM, one of the idoc is showing the message 'Application document not fully posted'. When i checked the status record it says that:
Message no. HRALX00_ORG246
In order to further process business partners, the system must determine the internal keys for the business partners. An error occurred when trying to determine these keys.
The error occurred in function module RH_ALEOX_BUPA_WRITE_O when calling BUP_PARTNER_GUID_CONVERT (error code 2).
If you have any inputs regarding the error, please help us.
Thanks & Regards,
Rahul.

hi,
go to the RFC destination that you use
to post IDOCs (from receiver IDOC adapter) - transaction SM59
and go to it's logon/secutiry tab
and check if the user which is defined over there
has the right authorizations to post idocs in R3
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Idoc WPUWBW: Status 51 - IDoc not fully processed

Hi All!
Hi All!
This is regarding Goods Moment.
In Quality, Idoc is successfully generated at POSDM system and also in ECC system.
In Production, Idoc is successfully generated at POSDM, but in ECC it is failed (Idoc WPUWBW: Status 51-IDoc not fully processed).
So, at WPER it is showing as In deficit of stock. But stock is available.
Kindly suggest me how to close this issue.
Note: PFA Below. Its the screenshot of the error at WPER.
With Regards,
Yarnagula Sudhir.

Dear Venu
Difficult to answer with this limited information. If you share some more info will be easier to help
regards
Manish

CRM Business Object BUS1006005 Not Showing In LSMW Object List

I am trying to use Bus. Object BUS1006005 in an LSMW using BAPI. I noticed that I need to generate an ALE interface for the object before LSMW can use it.. Can someone please help me with this? When I drop-down on Business Object in LSMW Attributes, this object does not show on the list, however I noticed that Bus. Objects with ALE Message Types do show up.
Kind Regards,
Jason

IDOC Type:It is the Structure and format of the data that is to be exchanged
see the EDBAS table
MESSAGE TYPE: Determines and Processes the various outputs associated with an application document . Mostly used in SD and MM modules
See the EDMSG table
see the link for LSMW-IDOC
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
LSMW-BAPI
Step-by-Step Guide for using BAPI in LSMW
Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions.
Introduction:
This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP.
Pre-requisites:
It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types.
Step-by-Step Procedure:
Details of the BAPI used in this scenario:
Business Object: BUS2012
Method: CreateFromData
Details of Message Type and Basic IDoc Type:
Message Type: PORDCR
Basic IDoc Type: PORDCR02
Lets have a look at the BAPI first, before proceeding to the LSMW:
1. Go to Transaction BAPI
2. Click on Search Button
3. Enter the value BUS2012 and select Obj.type(Technical Object Name
4. Press ENTER
5. Following screen appears:
6. On the left side of the screen, Expand the PurchaseOrder.
7. Select PurchaseOrder and double-click on the same for details.
Building LSMW using BAPI:
1. Go to Transaction LSMW.
2. Enter the Project, Subproject and Object information and click on CREATE.
3. Enter the descriptions for Project, Subproject and Object.
4. Now select Settings à IDoc Inbound Processing
5. IDoc Inbound Processing screen appears. Enter the required details as shown below:
6. Click on Activate IDoc Inbound Processing.
7. Click on Yes when prompted for Activate IDoc Inbound?
8. Hit on Back to return to the main screen.
9. Click on Continue (F8). Following Screen appears:
10. Select the Step 1 Maintain Object Attributes and select Execute.
11. Select the radio button Business Object Method and enter the following details:
Business Object: BUS2012
Method: CreateFromData
Hit ENTER
12. Save and click on BACK button. Following information message is displayed.
13. Now select step 2 Maintain Source Structures and click Execute.
14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on Create again to create the child structure. Following popup appears:
Select Lower Level and click on Continue. Enter the Item data structure name.
Click Save and hit BACK button to go to the main screen.
15. Select step 3 Maintain Source Fields and hit execute.
16. Enter the fields as shown below:
17. Click SAVE and return to main screen.
18. Select step 4 Maintain Structure Relations and click Execute.
Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
Select HEADERDATA and hit ENTER
Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
Click Save and return to main screen.
19. Select the step Maintain Field Mapping and Conversion Rules and click on execute. Maintain the Field Mapping as seen below:
20. Select step 7 Maintain Source Files and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
Save and return to main screen.
21. Select the step Assign Files and click on Execute.
Assign the file provided to the source structure. Here the same file is provided for both the structures.
Save and return to the main screen.
22. Select the step Read Data and click on Execute.
Click on Execute.
Return to the main screen.
23. Select the step Display read data and click on execute.
Click on the structure name to get the field level values.
24. Return to main screen and now select Convert Data.
25. Return to the main screen and select Display Converted data.
26. Return to main screen and select Start IDoc generation.
27. Now select the step Start IDoc Processing on the main screen.
28. Return to main screen and click on Create IDoc overview. Here the data record and status records of the IDoc could be viewed
It is given in screen shot.
http://www.****************
LSMW-IDOC
see this and do accordingly
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
Go through the steps
Hi please go through the following steps for IDOC method
Step 1. Run the transaction ( /nlsmw ) you will reach to the screen
Here you have to specify
Project : 060_BUS_TRANS
Subproject : SERVICE_TICKET
Object : SRV_TICKET_ZSVT
click on the execute button .you will reach the screen :
The screen shows the 15 steps to Run the lsmw
Step 2) select the first step ( Maintain object attributes) and click the execute button.After clicking on the execute button you will reach at. the screen
Here you have to specify ( MEssage type and basic type)
click on the BACK button
Step 3) select the 2nd step ( Maintain source structures) and click the execute button
Here you have to specify the source structures.
Step 4) Select the 3rd step ( Maintain source fields) and click on the execute button :
Here you have to specify the fields present in the source structure
Step 5) select the 4th step ( Maintain structure relationship ) and click on the execute button :
Here you have to specify relationship between source and target structures
Step 6) select the 5th step ( Maintain field mapping ) and click on the exécute button :
Here you have to map the fields between source and target structure. Also you have to apply conversion rules here if any
STEP 7) select the 6th step and click on the exécute button
Here you can define any fixed value or user define routines
Step 8) select the 7th step ( Specify files) and click on the exécute button :
At This screen we have to specify the files for This we should be in change mode .So please click on the button shown in the above screen. After clicking on This button you will be in change mode and will be able to specify the files :
Step 9) select the 8th step ( Assign files) and click on the exécute button
For assigning files yoy should be in change mode do the same thing click on the button as shown in the above screen :
Then assign the files to different structures.
Step 10 ) select the 9th step ( Read Data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Again click on the exécute button . After clicking on the exécute button you will reach to the next screen
Here you will see data is read.
Step 11) select the 10th step ( Display read data) and click on the exécute button :
Here you can see your test data present in test files assign to source sturcture
Step 12 ) select the 11th step ( Convert data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Click on the exécute button as shown on the : After click on the exécute button you will reach to the next screen
Data is converted
Step 12th ( Display converted data is same as Display read data )
Step 13 ) select the 13th step ( Start idoc generation) and click on the exécute
button :
At this step Idoc is generated using converted data
Step 14) select the 14th step ( Start idoc processing ) and click on the exécute button :
After clicking on the exécute button you will reach to the screen :
And then click on the exécute button : After clicking on the exécute button you will reach to the final processive screen
If data is processed correctly you will see ( 53 Status message with green sign)
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
Step-by-Step Guide for using BAPI in LSMW
Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions.
Introduction:
This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP.
Pre-requisites:
It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types.
Step-by-Step Procedure:
Details of the BAPI used in this scenario:
Business Object: BUS2012
Method: CreateFromData
Details of Message Type and Basic IDoc Type:
Message Type: PORDCR
Basic IDoc Type: PORDCR02
Lets have a look at the BAPI first, before proceeding to the LSMW:
1. Go to Transaction BAPI
2. Click on Search Button
3. Enter the value BUS2012 and select Obj.type(Technical Object Name
4. Press ENTER
5. Following screen appears:
6. On the left side of the screen, Expand the PurchaseOrder.
7. Select PurchaseOrder and double-click on the same for details.
Building LSMW using BAPI:
1. Go to Transaction LSMW.
2. Enter the Project, Subproject and Object information and click on CREATE.
3. Enter the descriptions for Project, Subproject and Object as prompted.
4. Now select Settings à IDoc Inbound Processing
5. IDoc Inbound Processing screen appears. Enter the required details as shown below:
6. Click on Activate IDoc Inbound Processing.
7. Click on Yes when prompted for Activate IDoc Inbound?
8. Hit on Back to return to the main screen.
9. Click on Continue (F8). Following Screen appears:
10. Select the Step 1 Maintain Object Attributes and select Execute.
11. Select the radio button Business Object Method and enter the following details:
Business Object: BUS2012
Method: CreateFromData
Hit ENTER
12. Save and click on BACK button. Following information message is displayed.
13. Now select step 2 Maintain Source Structures and click Execute.
14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on Create again to create the child structure. Following popup appears:
Select Lower Level and click on Continue. Enter the Item data structure name.
Click Save and hit BACK button to go to the main screen.
15. Select step 3 Maintain Source Fields and hit execute.
16. Enter the fields as shown below:
17. Click SAVE and return to main screen.
18. Select step 4 Maintain Structure Relations and click Execute.
Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
Select HEADERDATA and hit ENTER
Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
Click Save and return to main screen.
19. Select the step Maintain Field Mapping and Conversion Rules and click on execute. Maintain the Field Mapping as seen below:
20. Select step 7 Maintain Source Files and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
Save and return to main screen.
21. Select the step Assign Files and click on Execute.
Assign the file provided to the source structure. Here the same file is provided for both the structures.
Save and return to the main screen.
22. Select the step Read Data and click on Execute.
Click on Execute.
Return to the main screen.
23. Select the step Display read data and click on execute.
Click on the structure name to get the field level values.
24. Return to main screen and now select Convert Data.
25. Return to the main screen and select Display Converted data.
26. Return to main screen and select Start IDoc generation.
27. Now select the step Start IDoc Processing on the main screen.
28. Return to main screen and click on Create IDoc overview. Here the data record and status records of the IDoc could be viewed:
Please Go through these Links ,
BAPI with LSMW
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI
For document on using BAPI with LSMW, I suggest you to visit:
http://www.****************/Tutorials/LSMW/BAPIinLSMW/BL1.htm
http://myweb.dal.ca/hchinni/sap/lsmw_home.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
bapi-idoc:
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
Thanks
Naveen khan

Idoc not showing in R/3

Similar Messages

Maybe you are looking for