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

mass uploading

Former Member
0 Likes
567

hello frnds

i needs to mass upload the warranty claims data in 4.6C.

my requirement is : the user will get N number of IDOCS, which contains claims data, on daily basis and he will process them by his end of the day in forms of batches by scheduling them as background job.

kindly suggest how to move further???

regards

anjali

4 REPLIES 4
Read only

Former Member
0 Likes
504

Hi,

As it is an inbound process create a fm and attach it to a process code and arrach this in partner profile, and write all ur code for posting of the data in that FM.

Regards,

sasi

Read only

0 Likes
504

hello Sasi

will it work as batch process for mass uploading in 4.6C?

i checked it out but v thik this mass uploading of claims data is not supported 4.6C.

Regards

Read only

Former Member
0 Likes
504

Hi,

Here you will create a inbonund idoc and through the inbound idoc it will get the data form the other server immediatly..But here you have create the partner profile as per your requirement i.e. in partner profile there is is option like TRIGGER BY BACKGROUND PROGRAM.if you select this radio button these idocs will not update the data base immediately.You have to run the program RBDAPP01 program explicitly.So here you can run this program by batch run every day night and you will fulfil your requiremnet.

Thanks,

shyla

Read only

Former Member
0 Likes
504

Hi Anjali,

In the partner profile which you have created for the claims data message type, select the radio button saying 'Trigeer idoc processing by background job'.

This makes, all your incoming idocs to go into status 62.

And you can process these using program RBDAPP01.

Reward points if it helpful.

Thanks,

Prasanna

Edited by: prasanna j on Apr 3, 2008 9:54 AM