PO IDOC-Migration

Hi Gurus,
I need to migrate open POs from one SAP system to another SAp system thro ALE-Idoc.How to create idoc for the existing PO and how to maintain conversion rules ?how to send the idocs to other system?
P.S:All the settings for Distribution model ,partner profile are maintained .

Would you clarify your needs? what do you mean with "P.S:All the settings for Distribution model ,partner profile are maintained"?
Sorry I got confused since you put that you have all done.
tks

Similar Messages

Sales order Validation in CRM

Hi Guys,
I am working on migrating the sales order from 3.1i system to CRM. The sales orders from 3.1i is coming to CRM through idoc. So once the idoc migrates the data to CRM, i have to create an ALV report to validate the data and give the user an option wether to post it or not. So for validating th data, how can i link the data in iDOC to the report.
Regards,
Kochuus

Solved myself

IDoc for BP migration is in error on transferring from CRM 4.0 to 7.0

Hi,
We have a requirement to migrate Business Partners from CRM 4.0 to CRM 7.0. We are using the message type CRMXIF_PARTNER_SAVE_M for this purpose. The IDocs are generated correctly from CRM 4.0 and carry the correct data. The status of Idoc in CRM 4.0 is set to 03.
However, on checking in CRM 7.0 system, we found the IDocs to be in error with a status of 51. The IDocs fail validation on the Birthdate field - where first 3 digits are replaced by spaces.
Any suggestions on how to correct the birthdate field? There are no changes being done to the data during mapping on either the inbound or outbound site.
Regards,
Mugdha

Hello,
note 915509 (needs to be implemented manually) should solve this issue.
Best regards,
Christian

Best practice for migrating IDOCs?

Subject: Best practice for migrating IDOC's?
Hi,
I need to migrate some IDOC's to another system for 'historical reference'.
However, I don't want to move them using the regular setup as I don't want the inbound processing to be triggered.
The data that was created in the original system by the processed IDOC's will be migrated to the new system using migration workbench. I only need to migrate the IDOC's as-is due to legal requirements.
What is the best way to do this? I can see three solutions:
A) Download IDOC table contents to a local file and upload them in the new system. Quick and dirty approach, but it might also be a bit risky.
B) Use LSMW. However, I'm not sure whether this is feasible for IDOC's.
C) Using ALE and setting up a custom partner profile where inbound processing only writes the IDOC's to the database. Send the IDOC's from legacy to the new system. Using standard functionality in this way seems to me to be the best solution, but I need to make sure that the IDOC's once migration will get the same status as they had in the old system.
Any help/input will be appreciated
Regards
Karl Johan
PS. For anyone interested in the business case: Within EU the utility market was deregulated a few years ago, so that any customer can buy electricity from any supplier. When a customer switches supplier this is handled via EDI, in SAP using ALE and IDOC's. I'm working on a merger between two utility companies and for legal reasons we need to move the IDOC's. Any other data is migrated using migration workbench for IS-U.

Hi Daniele
I am not entirely sure, what you are asking, Please could you provide additional information.
Are you looking for best practice recommendations for Governance, for example: Change transports between DEV, QA and PRD in BPC 7.0?
What is the best method? Server Manager backup and restore, etc ?
And
Best Practice recommendations on how to upgrade to a different version of BPC, for example: Upgrading from BPC 7.0 to 7.5 or 10.0 ?
Kind Regards
Daniel

RDS for SAP data migration through IDOC's

Dear Experts
Just now we have installed BODS 4.1 and RDS also installed now. I am in the process of exploring the RDS. I found all the migration objects is available in the form of IDOC's. Now my questions are
How to work on custom IDOC's. Do i need to extensively code on R/3 side to upload the custom fields. Like user exit or BADI for custom fileds
If yes then i would say implementation time through RDS will remain more or less same time.
Through BODS or by RDS migration objects is there any way without coding on ABAP R/3 side, Can we achieve migrating custom fields
Please let me how to achieve above requirements by RDS
Thanks
Vijay Mukunthan

Hi Vijay,
You are right, the standard content of the Rapid Data Migration RDS packages brings the content with the standard IDoc interface for SAP standard only. So custom objects are not pre-built with the package. However, we incorporated the foundation to include custom coding as easy as possible:
1) IDoc
We are using the standard interface technology IDoc. IDocs do have an enhancement concept which is described in the online help. There are three main cases and all of them are supported, however two need additional coding:
Z-fields: Additional fields in existing tables lead to IDoc segment extensions
With the IDoc segment versioning concept this is easy to realize without any ABAP coding
Z-tables: Additional IDoc segments will be necessary and lead to a new IDoc version
With the IDoc versioning concept you can easily add Z-segments with leveraging provided user exits
Custom business objects:
You can even create a complete own IDoc message type in Z-namespace for own stuff, leveraging the given ALE layer of the IDoc middleware
2) Enhancement guide
With the RDS package we offer an enhancement guide which helps you to modify the jobs and data flows in the SAP Data Services content according to the changes in the target IDoc structure to reflect additional fields and tables. We built it as a step-by-step guide following for a sample IDoc type but will work similarly for any IDoc.
Best regards,
Frank Densborn.

Problems migrating data via LSMW using the IDoc method

Hello everybody,
I got a very strange problem migrating data via the LSMW. I tried to map legacy data using the IDoc mapping method. I'm using the message type 'CRMXIF_PARTNER_SAVE_M ' and the basic IDoc type 'CRMXIF_PARTNER_SAVE_M01'.
I can read the import data and convert it to IDoc structure as well as generate the IDoc. When I start processing the IDoc afterwards I get always the same error messages which I don't understand...
The errors are:
1) Error status 'A ' calling validation service (Status 51)
2) Validation error occurred: Module CRM_BUPA_MAIN_VAL , BDoc type BUPA_MAIN (Status 51)
3) Error_Time Dependency_Addresses CHECK_TABLE_MISSING (Status 51)
4) Internal error when calling operation module BUA_CHECK_ADDRESS_VALIDITY_ALL : Check table missing (Status 51)
5) Address moves ignored in the case of time-independent systems (Status 51)
6) Partner data processed with key PartnerGUID 4BF67ADE9B9923BEE10000000A3500DB (Status 51)
7) Partner (4BF67ADE9B9923BEE10000000A3500DB ): the following errors occurred (Status 51)
I tried to import the following data:
external ID
Name1
Name2
Address data
Telephone data
Fax data
Website data
Can anybody tell me where those errors come from and how I can fix them. Would be great if somebody could help me!
Thank you and best regards,
Markus

so apparently my issue with this was setting the time zone in the Address to the time zone of the user doing the conversion. You can find the time zone in SU01.
Also you can create a BP in the WebUI then check t-code SMW01 and it will help you on passing the values to CRMXIF_PARTNER_SAVE
Edited by: Akeem Lockett on Jul 8, 2010 7:44 AM

Data migration ALE or idocs and bapis

hi ,
thank you guys for the support.
i am into a data migration project.
i need the initial setup for the idocs and bapis.
i dont know anything about these so can u send me the process for the setup and the data migration process too with idocs and bapis.
i didnt understand when they asked me if we can data migrate with a ALE, is that the same as using idocs and bapis or is it a different approach.
u can send me at any inofrmation connected to my eamil addr.
i would really appreciate that.
thank you.

Hi,
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
for VA01 use BAPI_SALESORDER_CREATEFROMDAT2
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
Thanks and regards,
Sarada

ALE/IDOC for Data Migration of some master data

Are ALE/IDOC available for data migration of the following master data:?
1)General Tasklists in PM
2)Equipment Tasklists in PM
3)Single Cycle plans in PM
4)Strategy plans in PM
5)Equipments
6)Functional locations
7)Measuring points
8)Work Centers
9)Equipment BOMS
10)QM Info Records
11)Sampling procedure
12)Certificate Profiles QM
13)Inspection Plans
14)Material master-QM View
15)PP Recipes
16)Equipment BOM
If anyone has worked worked on ALE/IDOC for data migration, please guide

Hi Dirk ,
Thanks for your reply . Can we use matmas03 for loading. What will be the differences between these two IDOCS.

How to use IDoc. in data migration?

Dear Expert,
How can I use IDoc. method in Data Migration???

Hi,
You can use Idoc method in data migration using LSMW - Idoc method.
In LSMW select the Idoc method and give the Message type and Basic type according to your requirement.
Before that you need to maintain the Idoc inbound processing.
Goto LSMW initial screen,
LSMW -> Settings -> IDoc Inbound Processing. Maintain File port, partner type and partner no.
After maintaining the Partner no. goto WE20 (maintain partner no.) and add the message type in the Inbound parameters of the partner no. Also we need to maintain the Process code for the message type.
After all this settings we can use Idoc method for data migration.
The rest of the steps are same as other methods till convert data.
Regards,
Asif Ali Khan

Steps to migrate lsmw using Idocs

hello i need to migrate lsmw using idocs ?can anybody please tell me the ateps in idoc method
It's very urgent , help plz.
Thanks in Advance
jdkumar

goto--> lsmw.
settings--->idoc inbound processing
here enter file port, trfc port, partner name.
then follow below steps(as suggested above by a frnd)
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

Data Migration-LSMW using IDoc Method

Hi Friends,
I have contract relevant information in the form of a excel spreadsheet/tab delimited flat file.
This transactional data has information such as Header Data, Item Data and Sub Item data (BOM explosion).
I need to migrate this data from the flat file to the CRM application using the IDoc Method of LSMW.
/When I used the Batch Input Recording method, the item data was not captured during recording./
Kindly send me relevant information to [email protected]
Thanks in Anticipation
rgards,
Praveen

Hello Sven,
thanks for your comment. Unfortunatelly those both transactions do not exitst because I work on SAP CRM 7.0 instead of SAP ECC. I also looked for similar transactions in the table but didn't find anything.

EDI/IDOC changes required for Unicode migration

Hi Everyone,
We are planning to migrate our R/3 box to Unicode and have got suffiecient documents regarding the changes needed for the ABAP programs. But the EDI and IDoc process is proving to be a grey area in this regard. I would be thankful if some one can send the related documents.
email [email protected]
Thanks,
Vinay

If you have VS .NET 2003, then all you need to do is install CR XI Developer. I would not recommend using the RDC in.NET for two basic reasons:
1) The RDC has not been tested in .NET (thus no escalation is available for any fix issues)
2) The RDC has been retired in CR 12. This may have implications for the lifecycle of your project...
To see how to use the RDC in .NET, check out the article [Using the Report Designer Component in Microsoft Visual Studio .NET|https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/f0751a7f-a81d-2b10-55a0-e6df0e1bab6d&overridelayout=true]
My recommendation would be to use the CR assemblies for .NET. The following resources should get you going:
[Sample applications|https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsfor.NETSDK+Samples]
[Crystal Reports For Visual Studio 2005 Walkthroughs|https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/2081b4d9-6864-2b10-f49d-918baefc7a23&overridelayout=true] (most of the concepts will apply to .NET 2003)
[Advanced use of Crystal Reports for Visual Studio .NETu2019s feature set and object model|https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/702ab443-6a64-2b10-3683-88eb1c3744bc&overridelayout=true]
Developer libraries:
https://boc.sdn.sap.com/developer/library
http://devlibrary.businessobjects.com
Also, ensure you apply the latest CR XI r1 [Service Pack|https://smpdl.sap-ag.de/~sapidp/012002523100006008952008E/crXIwin_sp4.zip]
Ludek

Data migration with ALE/Idoc

Hello .
I want to migrate data between two SAP system using ALE / IDOC, and I want to know the settings to make on each system (source and target).
Does someone has an idea?
Thank you all

Outbound Settings
Define Logical Systems and Assign Client to Logical System u2013 Transaction SALE
u2022     Go to Define Logical System (See the figure)
u2022     Define a new logical system to identify the local system and save it
u2022     Now, go to Assign Client to Logical System (See the figure)
u2022     Add a new entry
u2022     Specify the client, previously created logical system and other attributes
u2022     Save the entry
u2022     Define a new logical system to identify the partner system and save it
Maintain RFC Destinations u2013 Transaction SM59
u2022     Create a new RFC destination for R/3 type connection
u2022     Specify the target host on Technical settings tab
u2022     Provide the Logon credentials on the Logon/Security tab
u2022     Save the settings
u2022     To verify the settings, Click on Test connection or Remote logon
Define Ports u2013 Transaction WE21
u2022     We need to define a tRFC port for the partner system
u2022     Click on Transactional RFC node
u2022     Create a new port
u2022     Provide a description
u2022     Specify the name of the target RFC destination
u2022     Save the object
Maintain Distribution Model u2013 Transaction BD64
u2022     Click on Change
u2022     Create a new model view
u2022     Provide a Short text and Technical name to the model view
u2022     Add message type
u2022     Specify sender and receiver systems
u2022     Also, specify the message type that we created previously
u2022     Save the Distribution model
Generate/Create Partner Profile u2013 Transactions BD82/WE20
u2022     To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles
o     Otherwise, you may use transaction WE20 to create a partner profile
u2022     On selection screen, specify the model view, target system and execute
u2022     The result log will be displayed on the next screen
u2022     To verify the partner profile go to WE20
u2022     Check the partner profile for the target system
Distribute Model View u2013 Transaction BD64
u2022     Select the Model View
u2022     Go to menu path Edit -> Model View -> Distribute
u2022     Result log will be displayed on the next screen
Inbound Settings
u2022     Define Logical Systems u2013 Transaction SALE (Please refer to Outbound Settings discussed)
u2022     Assign Client to Logical System u2013 Transaction SALE (Please refer to Outbound Settings discussed)
u2022     Maintain RFC Destinations u2013 Transaction SM59 (Please refer to Outbound Settings discussed)
u2022     Define Ports u2013 Transaction WE21 (Please refer to Outbound Settings discussed)
u2022     Generate/Create Partner Profile u2013 Transactions BD82/WE20 (Please refer to Outbound Settings discussed)
u2022     Assign Function Module to Logical message u2013 Transaction WE57
o     Create a new entry
o     Specify name of the Function Module
o     Also, specify Type as F, Basic IDoc type , Message type and Direction as 2 (Inbound)
o     Save the entry
u2022     Define Input method for Inbound Function Module u2013 Transaction BD51
o     Create a new entry
o     Provide Function Module name
o     Specify the Input method as 2
o     Save the entry
u2022     Create a Process Code u2013 Transaction WE42
o     Create a new Process Code
o     Select Processing with ALE Service
o     Choose Processing type as Processing by function module
o     Save the entry
o     On the next screen, select your function module from the list
o     Save the changes
o     Now you will be taken to the next screen
o     Double-click on Logical message
o     In the Assignment to logical message, specify the message type
o     Save the changes

Data migration through IDoc processing in LSMW

Hi all,
I have an requirement wherein i need to transfer material master data through LSMW conversion process into R/3 database.The data is to be posted through ARTMAS04 inbound IDoc.
The problem is to transfer the data simultaneousely through multiple instances of E1BPE1MARAEXTRT segment of ARTMAS04 IDoc.
for example:
I need to have an assignment that should work like this:
E1BPE1MARAEXTRT[]-FIELD1 = '00001'
E1BPE1MARAEXTRT[]-FIELD1 = '76545'
E1BPE1MARAEXTRT[]-FIELD1 = 'SAP'.
Can anybody help me in acheiving this example scenario in LSMW.
Thanks.

HI everybody,
i had solved the problem myself.
Thanks all.

CP issues during data migration through IDOC

HI,
We are migrating data from One server to another thru PFAL, but the CP data is not posted as it gives the error
Relationship starting from 01P 00093159 impossible - 01CP50002607 does not exist/is not active
is there a way to migrate the CP data ?

Hi
Check the BD64 configuration if the relationship is filtered out in the Message type.
Try sending the CP object first to the other server and then resend the person again. The error is because the The object is not existing the Target system.
Hope this helps, if so reward.
Thanks
Shyam

PO IDOC-Migration

Similar Messages

Maybe you are looking for