What is the best way to schedule a job for PI interface?

[Former Member]

Hi,

I have this PI scenario to implement.

Every day, something (?) needs to trigger PI to call RFC function, get the data and insert it to database.

What is the best practice to schedule such a job in PI?

I want to know best practice to trigger PI interface and how to schedule it.

Also, do I have to use BPM for this?

Thanks for your help.

-Won

Edited by: WON HWANG on Sep 10, 2010 11:21 PM

[Former Member · Accepted solution]

Hi Won,

it depends a bit on the scenario that needs to be implemented. I will try to go point by point and give you the options

1. You will need to send a message to PI

- This can be from PI or from ECC. I suggest you use an ABAP proxy client.

- You will need to write an ABAP program that sends this message (calling the proxy client).

- You can schedule this program in a job (SM37).

- If users want control over the job, better schedule it in ECC; if only you or an administrator will control the job, you can do it in PI

- I would use a generic format which you can reuse to trigger other interfaces: From- and To-date, Context, Action, User

- You can have conditions in the Receiver Determination and Interface Determination to route the message to the correct interface, based on the Context and Action for example.

- From- and To-date can be used to make selections in any RFC or table query.

2. You will need a BPM process in PI

- Step 1: Receive the trigger

- Step 2: Call the RFC

- Step 3: Send to database

this is because the RFC call is synchronous, and you cannot route the response to another receiver than the sender of the RFC call. Another options is writing a wrapper in ECC around the RFC function, and at the end implement another PI ABAP proxy client that will be routed to your database interface.

Hope this helps.

kr

Peter Glas

[stefan_grube · Accepted solution]

You do not need a BPM.

1. create an ABAP report

2. inside the report, you call the RFC locally

3. call a second (new) RFC or ABAP proxy asynchronously, where your request parameters are the response parameters from RFC

4. route this call direct to database table

schedule this ABAP report with SM37 as background job

[prateek]

something (?) needs to trigger PI to call RFC function,

Can't you schedule a job in the ECC system where RFC resides?

Regards,

Prateek

[Former Member]

Thanks for the response...

Since I'm new to PI and also not an expert in ECC, can you please explain more about scheduling a job in ECC?

Do I have to create another new RFC and trigger PI to call the existing RFC and get data?

Or do you have better way in mind?

Thanks again.

-Won

[prateek]

You may create a program and trigger the RFC inside that program. This program can be then assigned to a job scheduled in sm37 in ECC. Thats it.

Regards,

Prateek

[Former Member]

Inside the program, after calling the RFC and get the data, how do I send it to PI?

Thanks,

-Won

[Former Member]

U can send it through outbound proxxy....search on SDn about the process.

chirag

[Former Member]

Create RFC in ECC - application system.

Import it in PI.

Schedule job in ECC - app server to execute RFC.- It will pass export parameter to PI where you configured mapping using RFC structure.