CRMXIF_PRODUCT_INDOBJ outbound Bdoc / Idoc

Hi All,
I'd like to use the PRODUCT_INDOBJ BDOC and the resulting CRMXIF_PRODUCT_INDOBJ_SAVE01 IDOC to transfer some data to an external system. The BDOC and IDOC are correctly generated when I change the IBase components. I'd like to add some additional fields into the IDOC which are not in the BDOC.
In the past, I have implemented the relevant BADI provided by the XIF framework - i.e. for service orders I've implemented the CRMXIF_ORDER_MAP badi and this works fine.
I've tried implementing the CRMXIF_PROD_IO_MAP badi but the code doesn't seem to get called. I've tried putting a breakpoint in the implementation and a large wait statement. The BADI doesn't seem to get called. I have activated the implementation.
Any idea why the CRMXIF_PROD_IO_MAP Badi is not being triggered between the BDoc and IDOC generation?
I've put my code in the CHANGE_MAPPED_DATA_OUT method as this is an outbound interface.
Cheers
Richard

Hi,
Do you have any guide of how to Enhance a BDOC and Create Mapping With the IDOC to send it to an External System through XIF.
I'd appreciate any info.
Thanx in advanced
josemcu-at-/gmail=dot=com

Similar Messages

Outbound INVOIC02 idoc

Dear experts,
I need to trigger outbound invoice idoc (INVOIC02) not at event of printing invoice but through a scheduled process for invoices of the day.
Is some standard program available ?

Hi Aditya,
You would be looking to schedule program RSEOUT00 for those IDocs then. I think you would also have to look into the partner profiles in WE20 to make sure you aren't triggering them automatically.
Regards,
Ryan Crosby

Outbound Delivery IDOC not updating values from MKPF for goods receipt

hi all,
I have a question say I am generating an outbound delivery IDOC. which has fields Goods Issues & Goods Receipt date retrieve from MKPF(BUDAT).
say when i post goods issues, MKPF is updated and IDOC is gernerated with issues date taken from MKPF.
and when i tried to goods receipt, MKPf is updated and IDOC is generated but no receipt date taken from MKPF. then i check in MKPF, date is there and then once again I triggered the IDOC, receipt date comes......so my doubt is the time issues say when IDOC is triggeres, no value in MKPF...but when i check the time it is 4 mins difference from the MKPF time and the IDOC time...
and also 1 more thing for doing goods receipt, we do in different transaction and for good issue we do in Vl02n.
so bit confused.
kindly help

True , but in BKPF only Issues date are stored not the receipt date say if the document type = WE.
Please let me know is there any other options to fetch rather than MKPF.
because at the time of IDOC generation, there is not entries in MKPF. I tried to do using WAIT UP TO 50 seconds , even that didnt work.
Please guide me
thanks

How PO/Outbound delivery idoc can be triggered automatically once PO is created.

Hi All,
We have a requirement that we need to automate the process of generation of Purchase Order & Outbound Delivery Idocs as soon as they are created in using ME21N and VL02N standard tcodes.
Currently we are using ZDID Output type as craeted in NACE and below WE20 Message Control Entries:
For PO -
Application             EF : Purchase Order
Message Type:      ZDID : Direct Delivery PO
Process Code       ME10 : ORDERS: Purchase order
For OB -
Application        V2 : Shipping
Message Type:      ZLD0 : Delivery Note
Process Code       DELV : Delivery DELVRY01: DESADV/CARNOT/WHSORD/SHPORD
Also, BD64 entries are already maintained.
As per current process, we manually go to ME23N/VL02N tcode->and execute output type which generates Idoc in we02.
Can any one help me getting this automated urgently.
Thanks
neha verma

Hi Neha,
Use Change Pointers Concept for Both PO & Delivery Note.
So that, as soon as a Create/Change/Delete activities happen on PO & Delivery Note, IDOCS will be triggered automatically.
PO Change Pointers
http://scn.sap.com/docs/DOC-45107
Same setup for Delivery Note as well.
-santosh.

FM for outbound payment idoc

Hi,
How do we find out the FM for outbound payment idoc?.Here are the details
Message type-PAYEXT
Idoc type-PEXR2002
Thanks,

This thread is was last replied more than a year ago, but I'll add a little just to contribute.
WE60 documentation for the IDocs don't really give much except field / segment
information, but don't talk about where the fields come from.
FI_EDI_PAYEXT_PEXR2001_OUT seems to be the right FM, not sure how it relates to IDoc type pexr2002 as 2001 is the older version, but perhaps it handles the difference somewhere inside.
As to where certain segment fields come from (i.e. the mapping to master data fields...) , I've been debugging and still in progress.
I have not been able to find any straight forward mapping, and my comments at the moment are:
For any particular segment field of PEXR2002, take a look at FM :
FI_EDI_PAYEXT_PEXR2001_OUT
to see how it populates the field. Chances are, the values come from the tables REGUH/REGUP/REGUV.
The payment run process as far as my knowledge is concerned is as follows:
1) Payroll Run -> Stores to table BT
2) Pre DME (e.g. trx PC00_M08_CDTA) picks data frm BT and creates payment data in REGUH / REGUP / and REGUV tables. This gives you an identification feature ID for the next step.
3) RFFOEDI2 changes status field in REGUH for particular payment data record based on ID from step 2.. this enables it to be picked up in the next step.
4) RFFOEDI1 converts the record in REGUH into an IDoc which can be processed in BD87.
I have debugged from step 4 backwards to step 3, i.e. I know that segment field X comes from REGUH field Y. Now I have to debug step 2 to find out how it populates REGUH field Y. If this comes directly from master data, then that makes life easier. But if this REGUH field Y comes from table BT of step 1, then perhaps I have to debug the payroll run somewhere. (Nightmare?
Anyway, if anyone knows better, please advise.

Steps to create outbound CREMAS IDOC from ERP

Hi,
Can you please share the steps to create outbound IDOC from ERP system?
Business requirement is that whenever a new vendor is created in the ECC system, SAP should trigger an outbound vendor IDOC CREMAS from ERP system. Also whenever the vendor data is changed then the entire vendor details should be passed to outbound IDOC and not just the delta changes. Change pointer can be configured but to create idoc for full vendor records.
I guess we can use CREMAS.
Can anyone please share the steps to configure it in ERP?
Regards,
Sandeep

1. Read the file using OPEN DATASET and read and fill up the segment info and fill the EDIDC header data
and then call function
CALL FUNCTION 'INBOUND_IDOC_PROCESS'
    TABLES
      IDOC_CONTROL       = i_edidc
      IDOC_DATA          = i_edid4.
a®

Outbound error IDoc reprocessing

I have a scenario like whenever an outbound idoc is in error status, should be able to correct the idoc n reprocess it.
Suppose outbound idoc is in status 02. System process code will notify the agent assigned in partner profile. When i execute the workitem and corrected the port and try to reprocess, this status is set to 30. My requirement is once i correct the port status should become 03. How do we acheive this ? (not through report rseout00 )
1. In general scenario how do we handle outbound error idocs?
2. Is system process codes are used only for notifications or error processing?
Inputs will be appreciated regd outbound error reprocessing .
Thanks.

Hi Indira,
1. In general scenario how do we handle outbound error idocs?
You can use transaction BD87 to monitor the IDoc statuses.
and use the following programs to reprocess outbound and inbound error IDoc(s).
RBDAGAI2 - Re-processing of IDocs after ALE Input Error
RBDAGAIE - Reprocessing of Edited IDocs
RBDAGAIN - Process Outbound IDocs with Errors Again
RBDAGAIP - New Posting of Partially Posted IDocs
RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
RBDINPUT
2. Is system process codes are used only for notifications or error processing?
The process code ise used in both ALE and EDI framework to identify the function module or API (Application Programming Interface) to be invoked for subsequent processing. Inbound as well as outbound interfaces use process code but for different purposes. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.
Hoep this will help.
Regards,
Ferry Lianto

Split outbound ORDERS idoc to different ports

Hi All,
I was wondering whether it is possible to split an outbound ORDERS idoc and have it directed to two different ports based on document type? Client requires normal PO's to be written to one XML while STO's be written to a seperate file. Look forward to your responses.
Regards,
John

Hi,
These are the exits available for Outbound ORDERS idoc.
1. ORDERS Purchase order / order MM06E001 EXIT_SAPLEINM_001 Customer enhancements
for control
record: purchasing
document, outbound
2. ORDERS Purchase order / order MM06E001 EXIT_SAPLEINM_002 Customer enhancements
to data segments,
purchasing
document, outbound
3.ORDERS Purchase order / order MM06E001 EXIT_SAPLEINM_011 Final customer enhancement
EDI purchase
order outbound
You should create the project before implementing the exits. So that the break point is going to stop over there.
Check this link to know how to find BADI -
http://www.sap-img.com/abap/how-to-find-bapi-for-particular-transaction-in-sap.htm
In your case this BADI is there for the given program.

Why dont we need process code for outbound master idoc?

For inbound master idoc we need a process code (EX. matmas03-MATM) but for <b>outbound master idoc</b> why dont we need process code?can anybody clarify me on that.
thanx in advance....

plz clarify me on that...its urgent...

Convert IDoc outbound to IDoc Abstarct

Hello Friends,
Can any please tell me how to convert IDoc outbound to IDoc Abstarct type so that it can be used in BPM.
Thanks
Sam

Hi Woj,
Below is the xml message displayed.It says No Interface found .But I have all the objects at the right place.
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MATMAS.MATMAS04*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action INIT into MAST</Trace>
</Trace>
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MATMAS.MATMAS04*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface MIAbA_MATMAS_Req*</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
Also I have mapped IDoc_original_outbound to IDoc_asy_Abs _ED in my message mapping 1:1.I have selected original IDoc (not ED) in the receiver determination.
I don't think we need to explicitly maintain IDoc outbound asy in the MI..? should I..?
Kindly suggest me if you find any solution for this happening.
Please send me if you have any scenario of similar type else please mention the steps to be carried out for this scenario so that I can cross check with your steps.
Thanks alot for your valuable time.
Regards
Sam
Message was edited by: Sam
Guest

Userexit: Outbound matmas idoc

Hi Guys,
I am looking for a suitable userexit for Outbound matmas idoc.
The requirement is once the idoc number has been generated with idoc status AFTER that only i need a userexit for my own .
I am using BD10 transaction code to create the MATMAS idoc.
Will appriciate your help..!
Thanks,
Biswajit.

Hi,
The flow is like this in BD10....
CALL FUNCTION 'MASTERIDOC_CREATE_REQ_MATMAS'
   CALL FUNCTION 'MASTERIDOC_CREATE_MATMAS'
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'        " it return the control record with idoc no after execution
          CALL FUNCTION 'IDOC_CREATE_ON_DATABASE'    " it return the control record with idoc no after execution
              CALL FUNCTION 'EDI_DOCUMENT_CLOSE_CREATE_TAB'     " it return the control record with idoc no after execution
                      PERFORM F09_IDOC_INSERT_WITH_NUMBER USING IDENTIFIER    " idoc no generates here in control record
                                            DOCNUM
                                            IDOC_CONTROL
                                            SYNTAX_RETURN
                                            FREE_RETURN
                                            SYN_ACTIVE.
So i need a userexit / enhancement point after that with control record data.......

Outbound TRFC IDOCS are strucking

Outbound TRFC IDOCS are strucking in our production system with the status : "Transaction recorded". When we are processing manually through SM58 they are moving.
Can any one help me to resolve this?
Thanks in advance...
Regards,
Nani.

Hi
Have you checked , is this the issue everytime or generally when some big load is running ?
generally this happens when the transaciton queue gets filled up quickly and if the instances of LUWs in that queue take long time to process.
Please have look at the load and try to reduce data volume that need to be processed in one LUW this will lead to low run time of the excution of LUWs and can reduce the hanging up of your LUWs from being processed.
hope it helps in some analysis
regards
Vishal

Use IBAN number in outbound INVOIC IDOC

Hi,
I'm looking for a field to store the IBAN number in outbound INVOIC IDOC's. Apparently there is no separate field available for this. I would like to avoid extending the current IDOC structure and I would have expected the IBAN number to be part of the SAP standard outbound INVOIC idoc.
Has anyone encountered the same requirement? I have looked at the standard INVOIC01 and INVOIC02 structure.
Thanks
Walter

Hi Ken,
Thanks for the response. I'm indeed looking at the international bank account number.
I was hoping that SAP somewhere does have a solution to send the IBAN numbers and not that we have to overwrite the ACNUM field or create our own segment. I want to pass the regular bank account and the IBAN number in our IDOC so that we do not need to decide within SAP if a customer requires the IBAN number or any other number. We want to make that decision in our EDI mapping, not in SAP. I'm surprised SAP has not foreseen anything for this as the IBAN is widely used within Europe.
We already have a problem that we have more than 20 house bank with more than 20 bank accounts, so the SAP limitation of 20 K28 segments is already creating a problem for us.
I guess we will need to setup our own coding in the user exit. Thanks for your response anyway.
Regards
Walter

Outbound 855 IDoc Creation

Hi EDI Experts,
I have a requirement.
I want to send my outbound 855 IDocs out of SAP. But there is some twist here.
I cannot send my Outbound IDocs as soon as the Sales order is created. Once the sales order is created, at a later point of time an acknowledgement code will be added to the sales order. Only then I am supposed to send the IDocs out of SAP. (Infact IDocs should be created at that point of time). either batch or not is fine.
Any idea/suggestion how this can be achieved.
Ur comments are most valuable and welcome.
Thanks,
Matt

Thanks MxG for the Reply.
But I am just wondering what kind of output requirement i can use in this scenario.
2 - Order Completion.
Steps:
1.Inbound 850 IDoc comes into SAP and Creates an Order.
2. Outbound IDoc will be created (If Req is set to 2). But I don't want IDoc creation @ this point.
3. Order will be updated by an acknowledgement code by CR.
4. I need IDoc creation @ this point of time.
I am not seeing any Output Requirement that satisfy this condition.
What should I do??
Thanks Agai and waiting 4 ur reply
Matt
Edited by: Creasy Matthew on Jul 24, 2009 1:22 AM

Sales Order - Outbound Delivery IDoc scenario.

Hi Friends,
I have the below urgent requirement. I would be gratful, if someone suggest possible options.
Scenario: This is related to Sales order to Billing scenario.
We are creating Sales orders by using ORDERS05 Idoc. After the Real goods despatch happens at legacy system, we will be getting despatch feed (IDoc) for outbound delivery trigger. Here if all sales Order items are complete, the system is creating Outbound delivery by using this IDoc and then PGI will follow. This is Ideal scenario.
Practically what happening is, our sales orders are created with few incomplete items (Ex: Net price missing) because they are created via ORDERS05 Idoc.( Manually, we can't create sales order with incomplete items, unless we force the system to do so). When the Out bound delivery IDoc triggered, it will pick up only completed items and creates partial delivery and becomes 53 status. Now the sales order is left out with open and incomplete items.
Now our aim is how to make this outbound delivery IDoc fail, if this is not able to create delivery for all items?? (I mean, if the sales order items are incomplete, the delivery Idoc must fail. So later, if sales order becomes complete, this Idoc can be reprocessed again) How can we make this scenario possible??
Expecting your thoughts and inputs.
Regards,
Kaleeswaran

HI,
I suggest you to think of similar solution as below.
1.As your issue is at order (few items are incomplete with Pricing issue or some other issue), at sales order level while saving each sales order write the code in user exit_save_document_prepare to check if any items exists as incomplete. if yes then populate a delivery block in the sales document header.(you can use a new delivery block to distinguish the reason for the block)
2. While creating delivery for the order through Idoc since the incomplete orders have a delivery block at the sales document header level SAP wont create delivery for the entire Order.
3.Handling this delivery block at sales order header: when ever a sales order is popluated with this new delivery block triggere a workflow which will shoot a mail to your End user team or customer representative team. they will correct the issue in the order and remove the delivery block. if you dont want to go with a workflow then you need to incorporate a process to remove the delivery block in the sales order
Thanks,
Srini

CRMXIF_PRODUCT_INDOBJ outbound Bdoc / Idoc

Similar Messages

Maybe you are looking for