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.......

Similar Messages

USEREXIT for Outbound MATMAS

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.......

Userexit or Badi to change Outbound ORDERS Idoc

Hi all,
As per my requirement, I want user exit or Badi which can change Outbound Idoc for ORDERS. I am aware of enhancement MM06E001 with user exit EXIT_SAPLEINM_011. Here in our old system 4.6 we implemented same. But for our new system ECC 6.0 control is not going inside after changing PO, it is creating new Idoc & posting but not going inside same user exit. Is there any Badi available?
Is it because of version change?
Please its kind of urgent.
Point will be rewarded for helpful answers.
Thanks,
neo

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.

Multiple MATMAS IDoc getting created through RBDMIDOC program

Hello All,
I am creating MATMAS Idocs by RBDMIDOC proram, but as MATMAS message type is used in multiple distribution models ( i.e. MATAMAS is being sent to multiple partners), its creating multiple IDocs.
I want my IDoc to get triggered only for a particular partner. How can i acheive this ?
Searched on SDN but did not found solution.

As the standard settings, IDOCs will be transmitted to all the Partners which are maintained in WE20 (Partner Configuration). You can restrict the triggering of IDOC based on some condition using the Business transaction event MGV00100 (Publish & Subscribe). This event is called from Function module MASTERIDOC_CREATE_MATMAS (Line number 2074). Documentation of Standard FM SAMPLE_INTERFACE_MGV00100 reads
* Event rissen by the ALE outbound process for MATMAS.
* It allows to modify the idoc's control header the idoc data aswell
* as serialization information created by the standard SAP outbound
* process.
* Raising the EXCEPTION ERROR will prevent the IDOC from being
* submitted to the ALE layer.
* BE CAREFUL WITH ANY CHANGES TO IDOC_CONTROL. IT MAY EFFECT YOUR WHOLE
* ALE-SCENARIO
You have to copy the Standard FM SAMPLE_INTERFACE_MGV00100 to a Z function module and assign it using transaction code FIBF. Search SCN to get more details about configuring Business transaction events using FIBF.

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

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

FILE to IDOC SCENARIO NEED MANDATORY FIELDS IN MATMAS IDOC

Hi
I'm learning a scenario like File to Idoc which is i need some what are the mandatory fields for creting the message mapping.. between source file and MATMAS IDOC... because it was showing several fields.
is there any way to find out the fields we need to map compulsory... for sending IDOC successfully.
Thanks
Babu

Hi Babu !
Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
It will display a document, telling you which fields are optional and which mandatory.
Regards,
Matias
PS: please award points if helpful.

MATMAS idoc with classification details - reg

Hi,
I am working in a project related to the transfer of Material Master from one system to another ( Both are R/3 systems).
I am currently using the message type MATMAS with basic type MATMAS05. With the above message type i am able to generate an idoc from source system with all of the details except for the classification details.
For classification i have configured the message type CLFMAS and CHRMAS, in the CLFMAS i am able to successfully generate an idoc with BD91/BD92 tcodes. But when the idoc is generated, the idoc gives the list of charactersistics managed in the class at each segment level but not able to retrieve the values maintained by me during the material master creation. In order the target values for each of the characteristics in the class is empty.
Please clarify me with the following queries:-
a) Is that really required to push both CLFMAS and CHRMAS for a material master classification related field values ?
b) How to get the characteristics values maintained in the material master at the idoc level ?
c) How to link the CLFMAS generated idoc and the MATMAS idoc to link the relationship?
Thanks for the understanding.
Thanks and Regards,

Classification of a material has to be send with CLFMAS IDOC separate from the material.
Usually you first distribute all characteristics and classes, then the materials, finally the classification.
You have to enter the new material number in segment E1OCLFM field OBJEK of your classification Idoc.

Create a matmas idoc based on PIR information

Hello friends,
can you please help me on the following points please :-) ?
I need to create matmas idocs and these idocs should be sent on a web portal identified on our SAP system as a logical system. The vendors will have access only to the materials they supply. For this reason, I need to send in the matmas the GLN code corresponding to the vendor for which we have created a purchase information record. This way, on the web portal the display of matmas information will be organised according to GLN codes.
Question :
how can we create the MATMAS idocs according to purchase information records? I mean how can I create matmas idocs selecting the materials supplied by specific vendors???
is there any standard way to do it on SAP? or has it got to be done a specific way. and if so, do you have any idea on how to do it?
Thanks in advance for your very precious help,
Kind regards,
Karenn

are you thinking about manual creation in BD10, or something automatic?
BD10 has the standard F4 material search help.
If you need to do it regular and manually, then you may consider creation of a new included search help where you can search based on info records.

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.

Filtering out MATMAS IDoc based on a condition

Hi All,
       We are distributing a Material Master IDoc (Message Type MATMAS / IDoc Type MATMAS05) from an ECC 6.0 (WebAS 700) system to an external Non-SAP system via SAP XI.
       Now our requirement is that the users will maintain a Z-table with all the SAP plants that are relevant for the external system. They can add or delete plants from this table in the future
       If the MATMAS Idoc is created/extended for a plant which is not in the Z-Table then it should not get distributed.
E.g. If MATMAS IDoc contains plant 5000 and 5000 is not in the Z-Table then the Idoc should not even be created
We Tried a lot of enhancements: -
SMOD Enhancement - MGV00001
Enhancement Spot - ES_SAPLMV01 at different call up points
But none of them give the required exact result.
If we implement the enhancement spot inside the function module MASTERIDOC_CREATE_MATMAS, we get a message "1 Master IDoc created, 0 Communication IDocs created". So something is getting created and that's incomplete anyway.
So I am not sure how reliable this is
<b>One last approach I have is</b>: -
1) Send the IDoc to XI (without filtering)
2) Let XI look at the Plant code and compare with the Z-Table in ECC (via a Z-RFC function module) and then decide whether to send the IDoc or not send it to external system
Please let me know if my approch is correct or I am missing something here
Thanks and Regards,
Aditya

Hi Aditya,
If the Communication Idoc is not created it means that the IDOC is not sent out of the system. The Master Idoc creation does not mean the Idoc is sent to the XI adapter.
The purpose of Restricting at the Plant level will be satisfied if you delete the Idoc data with in the function module MASTERIDOC_CREATE_MATMAS.
It will work. Consequently you can add an additional check in XI to do this check, but this will increase the number of connections made to R3.
Hope it helps.
Thanks,

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®

Userexit: Outbound matmas idoc

Similar Messages

Maybe you are looking for