Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

No output type

Former Member

‎2007 Aug 21 2:04 AM

0 Likes
474

Hi,

If there is not output type setup is done as it is not required because there is nothing real time happening. Hence I will have to schedule background job for posting the IDOC, can anyone tell me if still I can send IDOC instead of file directly to the vendor.

Can anyone tell me the steps to follow the same.

Regards

Rinku

Hi,

If there is not output type setup is done as it is not required because there is nothing real time happening. Hence I will have to schedule background job for posting the IDOC, can anyone tell me if still I can send IDOC instead of file directly to the vendor.

Can anyone tell me the steps to follow the same.

Regards

Rinku

Reply
2 REPLIES 2
Read only

Former Member

‎2007 Aug 21 2:15 AM

0 Likes
443

Hi Rinku,

Even if you do not have anything real time, you can have an utput type defined in NACE transaction for EDI and then set the Dispatch Option as Send with Periodically Scheduled Job(In Further data). This way, your Idocs woudn't get triggered as and when you save the document, but you can process them at a later point in time.

Regards,

Ravi

Read only

Former Member
In response to Former Member

‎2007 Aug 21 2:30 AM

0 Likes
443

Thanks Ravi for your reply it really helped. I would appriciate if you can confirm me the steps as follows for EDI setting. Also I will have to write a custom function module as I need to fill IDOC fileds from custom table and from VBAK, VBAP and LIPS so was wondering if have to write the logic in Z functyion module.

• Idoc type – DESADV01 Transaction WE30.

• Message Type – DESADV Transaction WE81.

• Assign Message Type to Idoc type – Transaction WE82.

• Create a distribution Model - Transaction BD64.

• Update outbound parameters of the Partner profile – Transaction WE20.

• Assign custom function module to Message type.

• For the Logical system A for the above message types update the partner profile.

For each message type specify the Port and the IDoc types. ( Note : Port definition need to maintained using transaction WE21 and it has to be defined as a Transactional RFC port with RFC destination for system specified, which need to be maintained using SM59 ).