PO Collab using PORDCR1 : Unable to trigger outbound Idoc on PO Change

Hi All,
I have done the following config for sending PO's from ECC to PI:
a. Message Determination:
Application = EF
Output Type = BAPI
Program = BUS2012_ICH_R3
Form Routine = SEND_PORDCR1
Transmission Medium = 8 (Special Function)
Dispatch Time = 4 (Send Immediately)
Have maintained condition records for the desired vendors with Function == LS, Partner == Partner No. for SNC Logical system
b. Partner Profiles:
Maintained an outbound partner profile under SNC Logical System with the following details:
Message Type = PORDCR1
Receiver Port = PI Port
Basic Type = PORDCR102
Trasnfer Idoc Immediately == Yes
But I have not maintained any entries under Message Control
Error:
1. Able to successfully trigger Idocs for New POs created in ECC.
2. But there is no Idoc output when PO is changed / deleted.
3. For the Chnaged PO on clicking on Messages, can see an output entry after change but it is in the status "Not Processed"
Am I missing any addtional config for trigerring Idoc on PO Chnage / Deletion ?
Regards,
Bharath

Hi Nikhil,
I tried the following Message Control settings for Message Type - PORDCR1 / Partner - SNC Logical System:
a. Application = EF; Message Type = BAPI; Process Code = ME10 ; Change Indicator = Checked
b. Application = EF; Message Type = BAPI; Process Code = ME11 ; Change Indicator = Checked
c. Application = EF; Message Type = BAPI; Process Code = ABI_AIDN_OUT (the only option available in dropdown) ; Change Indicator = Checked
I tried chnaing an existing PO after saving each of this setting. There is not outbound Idoc that is getting trigerred.
Regards,
Bharath

Similar Messages

How to trigger outbound IDOC when data changed in BP through Inbound IDOC.

Hi,
    In our system whenever we create a new Business Partner, these data is send across to SAP R/3 (as BDOC) and to Mainframe system (as outbound IDOC). Whenever we change any Business Partner record the data is send across to SAP R/3 (BDOC) and to Mainframe system (as outbound IDOC).
    This functionality is working fine.
    Currently we are getting a value for one standard field (Customer_Group3) of Business Partner as an inbound IDOC. The value of the inbound IDOC is reflecting in the field (Customer_Group3) in Business Partner Transaction. Once the inbound IDOC is received, the modified value is send across to SAP R/3 as BDOC. But the modified value is not send across to Mainframe system (outbound IDOC). The outbound IDOC is not getting triggered.
Kindly help

Is your mainframe system configured as Site in SMOEAC. If so are you using XIF Adapter.

Trigger outbound idoc whenever PO is CHANGED and then saved

hi guru's
i am trying to trigger outbound idoc whenever PO is CHANGED and then saved .
i have created partner profile
PARTNER TYPE : LI
MESSAGE TYPE : ORDERS
BASIC TYPE : ORDERS05
APPLICATION : EF
PROCESS CODE : ME11
BUT, NOT ABLE TO CREATE CONDITION RECORD .
please guide me for the same considering i am new to ale-idoc

Hi,
Try to use the Message type as ORDCHG and processing code ME11.
In NACE transaction-->application EF --> copy the std output type 0003 to Z output type.
In this type in the default value tab enter the VN or LS.
In we20 :
Create the partner profile in the LI or LS .
message type as ORDCHG
process code : ME11
message type : output type which you created
Application :EF

Trigger Outbound Idoc on Customer Master change/ Create

Hi everyone,
can anyone provide me some information on how to trigger outbound IDOCs when a customer master is changed/created and which IDOC should be used.
Kind Regards,
Julian

Hi Julian,
For the automatic transfer of master data ,we can use change pointer technique.
Following are the steps to be followed:-
1) Enable change pointer globally (t.code BD61).
2)Enable Change Pointers for a Message Type (t.code BD50).
Here you have to check the Active checkbox corresponding to customer master message type 'DEBMAS'.
3)Specify the Fields for Which Change Pointers Are to Be Written (t.code BD52).
Various number of fields are present here corresponding to message type'DEBMAS'. If you want to add any other field , you can add here.
Apart from above three settings, all other ALE configurations are required like( partner profile, distribution model etc.)
For triggering the Idoc program 'RBDMIDOC' should be scheduled.
When you make any change in the customer master , Idoc will be triggered automatically from your SAP system.
regards,
monica

Auto trigger outbound IDOC

Hi, everyone:
I just want to know how to auto trigger outbound IDOC to non-SAP system. For example, Customer Master IDOC DEBMAS05, Masterial Master MATMAS05.
I know we can use changer pointer, But we need run the program 'RBDMIDOC'. I want the system will create IDOC when we click 'SAVE' icon.
Does somebody have any idea? Thanks.
cdspi

cdspi cdspi,
if the IDOC / Message type is set for immediate processing, it will be procesed immediately.
Regards,
Clemens

Trigger outbound IDOCs for EDI - CONTROL & APERAK messages

Hello All,
We have a scenario that customer transmits their EDI - ORDERS message and upon receipt of ORDERS, requires us to forward CONTROL and APERAK for any issues with ORDERS message. Checked different outputs and did not find suitable one. WIll appreciate, to know, the corresponding message/idoc types for CONTROL and APERAK and how to trigger.
Thanks in advance,
Renu

Hi Nikhil,
I tried the following Message Control settings for Message Type - PORDCR1 / Partner - SNC Logical System:
a. Application = EF; Message Type = BAPI; Process Code = ME10 ; Change Indicator = Checked
b. Application = EF; Message Type = BAPI; Process Code = ME11 ; Change Indicator = Checked
c. Application = EF; Message Type = BAPI; Process Code = ABI_AIDN_OUT (the only option available in dropdown) ; Change Indicator = Checked
I tried chnaing an existing PO after saving each of this setting. There is not outbound Idoc that is getting trigerred.
Regards,
Bharath

Change Business Partner in CRM to trigger OutBound IDOC in R/3 system

Hi Team,
I am stuck on a requirement, We have a scenario were the Business Partner is created in CRM system
which creates a BDOC and is passed to R/3 system through an Inbound IDOC which triggers the Outbound IDOC to PI system. So far good.
The scenario we are getting stuck is when a Business partner is changed in CRM an IDOC triggered in R/3 system but this being a change the Change pointers are not called hence the IDOC which is supposed to be triggered for the PI system is not getting triggered.
Can you please tell me what steps should I take to trigger this Outbound IDOC from R/3 system?
I did some anlyasis and found a table which COM_BUPA_CALL_FU which contains a set of function module which is triggered in the sequence. Is this the solution or if you have any different do let me know.
Thanks,
Imran

Hi,
Did you add the entry for your new custom 'Z' long text inPITX Tcode in R3 side. Every long texts in CRM should be linked to R3 long text here. If there is no entry please add one and try changing the text in CRM.
Hope this helps,
Karuna.

VL01N - needs to trigger outbound idoc

Hi all,
As per requirement please tell me information of how to trigger the outbound idoc on save that consist of delivery data with ref to sales order data.
I am not able to create the Output type please tell me steps if possible of provide me some link that helps me.
Regards,

Hello,
You have to create an OUTPUT in the configuration and maintain the condition records in VV21 for the Partner LS which means an output for IDOC
For this configration, Goto the spro
SPRO->LOGISTIC-EXECTION>SHIPPING->OUTPUT DETERMINATION->MAINTAIN OUTPUT DETERMINATION FOR OUTBOUND DELIVERIES---.DEFINE OUTPUT TYPES.
Try to create the output type and maintain the condition records .
Revert back if you need any clarifications
regards,
santosh

Trigger outbound idoc for F110 program

Hi Experts,
I am new to idocs, please anybody can help
regarding to create outbound idocs when i run F110 program.
when i run F110 with parametrs company code and payment method, automatically it will create idoc and send it to partner system.
i think i have to use pexr2002 and message type payext.
please help me on my request, it is very urgent work.
Regards,
Venkata

Follow the steps:
1) Do relevant Settings for payment program ( FBZP).
2) Example: For the house bank you have to set the EDI partner profile no. and the EDI partner profile and EDI compatible payments methods.you have to attach the payment methods to the house bank EDI profile. And check generate
EDI immediately in we20.
3) Create the partner profile for bank with message type " PAYEXT", partner
type " B". AND THE IDOC BASIC TYPE AS " pexr2002".
4) when you run the payment, the IDOC will be generated.
REfer to:
http://help.sap.com/bp_bblibrary/500/Documentation/W25_BB_ConfigGuide_EN_US.doc
http://www.sap.com/usa/solutions/business-suite/erp/financials/pdf/BWP_%20SAP_In-House_Cash.pdf
Reddy

Problem in Outbound Idoc Scenario with change pointers

Hi All,
I have a requirement where i have to create an outbound scenario, whenever i create or change in transaction PAL1 (Create Sales Representative), an idoc should be triggered.
i have created
- ZBasic idoc type
- ZSegments
And have assigned the ZBasic Idoc type to ZMessage type
Even I have maintained the fields to be triggered during change pointer in transaction BD52
Now my problem is, whenever i change a field in transaction PAL1 or create a new one, change pointer is not getting triggered via RBDMIDOC program.
Do we need to add an additional code to populate the Zsegments?
If so... can you send me the logic or Sample Code which fits my scenario?
Thanks.

Satish,
you cna check this badi HRALE00OUTBOUND_IDOC
Thanks
Bala Duvvuri

Unable to receive the IDoc sent in the recipient system

Hi All,
We have written a custom program to trigger outbound IDoc using Master_Idoc_distribute, it shows Idoc with success 03 status.
But an IDoc has not been received at the recipient system end and it shows a message com.sap.mw.jco.JCO$AbapException: (126) NOT_FOUND: NOT_FOUND. We find the system pointing to this same message at SM58 transaction, function module IDOC_INBOUND_ASYNCHRONOUS
The basic config have been done in these transactions WE31, WE30, WE81, WE82, BD69, WE20.
Kindly suggest what is missing.
Is there any other FM which needs to be called after Master_Idoc_distribute
Regards,
Priya

There have been some issues where Unity falsely detects Exchange being offline.A change was made in and after 7.0.2ES21 to change how we determine if the store is on or offline. This came out of CSCsx59710.
The following has been recommended:
Upgrade to the latest ES.
Change the "Startup Type" of AvMMProxySvr from "Automatic" to "Manual".
Make sure that "HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\AvWM\1.00\Check Level" is set to 0xF0.
Reboot.
So I suggest checking these things.
The issue can also be related to permissions. You might either run permission wizard again or run the latest permission wizard in reporting mode to determine if it reports any permission related issues.
Thanks,
Scott

Steps for configuring Outbound Idoc OILSHI01

Hi experts,
    can anybody tell me the steps how to configure an Outbound IDOC.
    It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
    if not anything else will also do.
    Kindly give me steps in detailed. Since i have never done this. Including
    distribution modle (BD64). in which case it generates the Automatic Partner
    profiles.?
<REMOVED BY MODERATOR>
Regards,
Umesh
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

Hi Umesh,
Sorry for the late reply. Let me clear your couple of misconceptions first.
Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
Now the further steps:
Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
2. Again, ask your functional consultant, as to which output type is configured for your business transaction. Select that output type and go to "Processing routines".
3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc.
Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
     a. trigger the idoc on saving the doucment. this triggers idoc as soon as you save the idoc.
     b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
     c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
Hope this was helpful.
<REMOVED BY MODERATOR>
Cheers,
Karan
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM

Nace config for DESADV type Outbound IDOC of type 856 at Delivery level

Hi All,
My requirment is to trigger Outbound IDOC of type 856 at delivery level & not at shippment level & one line per ASN.
How can I configure this in NACE?
Thanks in Advance.

Hi Raj,
For example, you can use the ASN0 output condition as a SAP standard. please go to NACE t-code and select the V2 for shipping and
go into the ASN0 output type configuration. in the that sceen;
1)give access sequence regarding of your requirment, for general data.
2)in the default values tab, Dispatch time can be 4= send immediately (when saving the application), transmission medium should be A Distribution (ALE) and partne function SH.
3 go in to the processing routines for the output type and Programcan be configured as RSNASTED, Form Routine as ALE_PROCESSING. But these are SAP Standard and they are changing your requirements with the ABAP tricks.
After the output type configuration, go in to the output condition from nace t-code same. And create condition for ASN0 output type. when creating your conditions regarding of your acces sequence, you should Dispatch time can be 4= send immediately (when saving the application), transmission medium should be A Distribution (ALE) and partne function SH like output type configuration,too.
I hope these will very useful to meet your requirements. But additionally, you should also contact with a ABAPER for the program and routines.
Regards,

User exit , transaction F110, an outbound Idoc

Hi,
During the payment process in transaction F110, an IDOC is generated. I need to identify the user exit within the IDOC build process to do some special processing.
The special process is to substitute the POSTING DATE on the IDOC with the NEXT PAYMENT DATE from the proposal.
Regards,
Jyoti Shankar

Hi Joyti,
I have requirement to trigger outbound IDOC after generating payment document....as your reply i think you already did this requirenment.
Kindly help how to configure outbound IDOC for this............
Plse reply me soon....
Thanks.

Outbound IDOC process - Using standard or Custom Program

Hi all,
i'm having some doubts regarding IDOC's outbound processing.
I'm trying to understand 2 scenarios:
1- Trigger Standard Outbound IDOC without writting any Z program ou IDOC FM.
It's possible to trigger a outbound idoc for exemple, whenever a sales order is created. To do this is, i suposed i don't need to write any code at all, correct?
What i need to do is create a logical system (SALE), define Transmission protocol (WE20, in here i associate the partner, and the outbound message type? After this point is the idoc automatic triggered?
If not, what is the correct procedure?
2 Trigger Ountbound IDOC using Z program.
Whats is diferent from the point 1 to this situation?
Best regards,
Pedro

Kali,
1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
3.Again ans is same as in point 1.

PO Collab using PORDCR1 : Unable to trigger outbound Idoc on PO Change

Similar Messages

Maybe you are looking for