Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Cross-client material transfer with conversion.

naimkhans_babi
Active Participant
0 Likes
673

Hi....

I have a problem to solve....i am supposed to transfer material data from client 040 to 041 with conversions. I am thinking to do it by ALE. what conversions i am supposed to perform is not yet decided by project manager so as ALE is not very flexibe in certain areas...is it worthy to use ALE and what would be another way to carry out this task... please help me in this problem...any article or suggestion will be great help of mine....thanking you,,,,

1 ACCEPTED SOLUTION
Read only

christian_wohlfahrt
Active Contributor
0 Likes
574

Hi!

? Strange. At least not easy. Do you speak about a development system? Maybe you just make a client copy and some hard database changes. Won't be OK, but if you just need some data for a performance test, this could do.

Test for a migration? Try to stay as close to the final way as possible.

You might save the outbound IDOC into a file, make some search and replace (in easy cases even in an editor) and upload the file for inbound IDOC. Also a report for file conversion can be used.

User-exits for IDOC segment changes might be possible, but doesn't look like a good idea (one-time special rules, but coding for all the time and everywhere).

Direct table copy is out of scope (e.g. because of internal number ranges).

LSMW might be an option, too. As input file you could again use outbound IDOC saved as file (with conversions?). Then inbound conversion would be in a transparent and easy to maintain way.

Hope you got some new ideas,

regards,

Christian

2 REPLIES 2
Read only

christian_wohlfahrt
Active Contributor
0 Likes
575

Hi!

? Strange. At least not easy. Do you speak about a development system? Maybe you just make a client copy and some hard database changes. Won't be OK, but if you just need some data for a performance test, this could do.

Test for a migration? Try to stay as close to the final way as possible.

You might save the outbound IDOC into a file, make some search and replace (in easy cases even in an editor) and upload the file for inbound IDOC. Also a report for file conversion can be used.

User-exits for IDOC segment changes might be possible, but doesn't look like a good idea (one-time special rules, but coding for all the time and everywhere).

Direct table copy is out of scope (e.g. because of internal number ranges).

LSMW might be an option, too. As input file you could again use outbound IDOC saved as file (with conversions?). Then inbound conversion would be in a transparent and easy to maintain way.

Hope you got some new ideas,

regards,

Christian

Read only

Former Member
0 Likes
574

These are the realted Tcodes fot ALE Conversion for any data.

BD55 Maintain IDoc Conversion

BD62 Define Segment Conversion Rule

BD79 Maintain IDoc Conversion Rules

Select a rule type

1) Copy sender field

2) Set Constant

3) Set Variable

4) Convert Sender fields

5) Convert/Copy

6) Use general bole.

And also u can do filtering in BD64 like plant level,Company code level or the material type etc.

Thanks

Eswar