Problem in triggering MATMAS IDOC through BD10 transaction

Hi,
My scenario is to trigger an IDOC(MATMAS)in BD10 and store it as an XML file in the physical directory.
I have created a logical system for this and also created partner profile for the logical system defined.
Further i've have configured XML Port has my reciever port of the outbound message type(MATMAS). But when i trigger the IDOC, it says that "1 Master IDOC setup for the message type MATMAS" and "0 Communication IDOCs generated" and the outbound IDOC is not recieved at the concerned directory. Please help me out in solving this issue.

Hi,
While doing configuration u must take care of creation of Distribution model. Here you need to give message type,sender & receiver.
At the same time you need to generate partner profiles. Results should give 'SYNCH' along with all info.
Check all the inbound/outbound parameters are correct or not.
If you satisfy with this pls close this issue and allocate some points.
Regards
KER.

Similar Messages

Triggering MATMAS IDoc

Hi Folks,
I have a requirement to send IDocs to the other system on create or change of material. On any create or change of material I want a MATMAS01 IDoc to be triggered and to be sent to the partner system.
1. I have chceked the Active checkbox for MATMAS in the tcode BD50.
2. I have saved the Change pointer in the tcode BD61
3. I have created the partner profile added the message types to it in the outbound parameter.
4. I have created the distribution channel.
But the problem is the IDoc is not triggering automatically once the material is created or changed in the source system.
Kindly let me know how to resolve this.
Regards,
Santosh

Hi,
Activating the change pointer for the mnessage type wont create the Idoc, you need to manually or schdueld prog to create the idoc against chage pointers.
Via change pointer, you have to run BD21 transaction or need to schedule RBDMIDOC to create an idoc.
If its a new material you need to run BD10 transaction.
Hope you clear, if not pls come back.

Triggering outbound idoc from the transaction VL01N

Hi,
I have requirement where in which i need to create outbound idoc of sales and delivery data as soon as VL01n transaction is saved,Pls let me know how we can achived this , the Idoc needs to be triggered immediatly after saving VL01n transaction.
Thanks
Ravi

>
Sujatha Reddy wrote:
> Hi Ravi,
>
> Goto t-code NACE, select Shipping and press push button 'Output Types', now you will get the output type for delivery and you can configure you own output meduim in this screen.
> select the meduim & assign the require parameters.
>
> and goto VL01N and create a delivery and now you can goto extrats-> delivery out put-> header, here you can assign the output type that has been confugured perviously.
>
> -hope this helps
You could of instead told them to search the forum like I did. Instead you chose to give him the answer, even though it is not the full answer. After they have done what you ask, what result would you expect form the output record on the delivery. I will tell you, it will not process, why, because you have not mentioned anything about partner profiles and the output control.
But I hope you get the points for you reponse and you sleep well.

Triggering workflow template through any transaction

Hi,
what is he procedure to be followed so that I can trigger workflow template through any transaction code, the requirement is to create a module pool program and that program should trigger a workflow template, so my question is what all classes have to be called that will trigger the workflow template.
Thanks and Regards,Neerup.

Check the following links:
http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/WORKFLOW_tutorial.html
http://www.sap-img.com/workflow/sap-workflow.htm
http://sapmaterial.com/workflow.html
http://****************/Tutorials/Workflow/Workflow.htm

Problem in triggerring EDI idoc for Purchase order..

Hi experts,
I am trying to create an outbound EDI IDOC for a PO.
I have configured the partner profile in partner type LI with message type ORDERS in outbound parameters. I have created a new output type ZEDI for EDI, and entered in a message control, as application EF, message type ZEDI and process code ME10.
But when i go to the me23n and goto--> messages, but when i click F4 for output type i am not able to see the new output type ZEDI i have created.
And if i also enter NEU with medium EDI, and Partner function VN, and partner 3000(where i configured the parnter profiles), its giving an error as, "maintain outgoing EDI-connection data for partner 3000".
Kindly help me out. please experts reply me..
Nithin

Hi
In the transaction NACE
you need to maintain the necessary 'Z' output type, in your case.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Problem in triggering the correct workflow on AdobeForm submission for PCR

Hi All,
I am facing a problem involving triggering of workflows through Adobe form submission. I have created a scenario for "Employee seperation" in QISRSCENARIO transaction and assigned it to an approval workflow. I have also activated and assigned the BUS7051-Created event in the workflow Basic Data. My workflow also triggers perfectly when i submit the adobe form. Everything is perfect till here.
Now i have to create another scenario for "Request for Transfer" Now for this i had to create a seperate workflow. My problem is since both these workflows are assigned to the same event whenever i submit the "Employee seperation" form both the workflows get triggered. Is there a setting where i can configure the corresponding workflow to be triggered for the respective scenario's alone? How do we handle this situation?

Hi Jocelyn/Raja,
I am trying to use SWB_COND for differentiating between the different workflows. I have created a virtual attribute W_SCENARIO_KEY for this. I tried populating this scenario key by using the following staement,

CALL FUNCTION 'ISR_SPECIAL_DATA_GET'
EXPORTING
 notification_no = object-key-number
IMPORTING
 SCENARIO = w_scenario_key.
SWC_SET_ELEMENT CONTAINER 'W_SCENARIO_KEY' W_SCENARIO_KEY.
When i try to include W_SCENARIO_KEY as a start condition the workflow shows up an express message and fails to trigger. In ST22 i can see that there is an exception "INVALID_NOTIF_NUMBER" raised.
But if i don't set this as a start condition all the workflows activated to BUS7051-CREATED are triggered and in the WF logs i can see the correct value of W_SCENARIO_KEY for the respective notification number.
I am not sure why this happens when i set it as a start condition alone.
I instead used a select statement as shown below,
select * from viqmel into table itab_VIQMEL
 where qmnum = object-key-number.
loop at itab_viqmel where qmnum = object-key-number.
w_scenario_key = itab_viqmel-auswirk.
endloop.
After inserting this statement it works fine without any issues. Any idea on why ISR_SPECIAL_DATA_GET cant be used in the virtual attribute implementation?
The following is the dump i get if i use ISR_SPECIAL_DATA_GET,
Information on where terminated
 The termination occurred in the ABAP program "SAPLQISR9" in
 "ISR_SPECIAL_DATA_GET".
 The main program was "RSWDSTRT ".
The termination occurred in line 39 of the source code of the (Include)
 program "LQISR9U01"
 of the source code of program "LQISR9U01" (when calling the editor 390).
Source Code Extract
Line SourceCde
9 *" EXCEPTIONS
10 *" NO_INTERNAL_SERVICE_REQUEST
 11 *" INVALID_NOTIF_NUMBER
 12 *" INT_SERVICE_REQUEST_NOT_FOUND
 13 *"----
 14
15 * local data
16 DATA: lt_dummy TYPE qisrsgeneral_param.
 17
18 DATA: lr_isr_document TYPE REF TO cl_isr_xml_document.
 19
20 DATA: ls_notif TYPE qmel.
 21
22 * MAIN
23 * try buffer first
 24 CALL FUNCTION 'ISR_SPECIAL_DATA_BUFFER_GET'
 25 IMPORTING
26 ET_SPECIAL_DATA = special_data
 27 ED_SCENARIO = scenario
 28 EXCEPTIONS
 29 BUFFER_EMPTY = 1.
 30
31 IF sy-subrc eq 0.
 32 EXIT.
33 ENDIF.
34
 35 * check notification number
 36 SELECT SINGLE * FROM qmel INTO ls_notif
 37 WHERE qmnum = notification_no.
 38 IF sy-subrc NE 0.
>>>>> RAISE invalid_notif_number.
 40 ELSEIF ls_notif-auswirk IS INITIAL.
 41 RAISE no_internal_service_request.
 42 ENDIF. 
43
44 * set scenario
 45 scenario = ls_notif-auswirk.
 46
47 * read ISR XML document
 48 CALL METHOD cl_isr_xml_document=>read_for_display
 49 EXPORTING id_notif_no = notification_no
 50 IMPORTING er_isr_xml_document = lr_isr_document
 51 EXCEPTIONS bds_error = 1.
 52
53 IF sy-subrc NE 0.
54 RAISE int_service_request_not_found.
55 ENDIF.
56
57 * read data from XML document
58 CALL METHOD lr_isr_document->get_data_from_xml

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.

Sending IDOCS through transaction PFAL

Hi,
We have a requirement to send idocs through transaction PFAL for a set of PERNRs for all infotypes.What is the way to go about this?
Thanks ain Advance!
Regards,
Nejuma Iqbal

hi
you cannot send IDocs thru PFAL transaction.
you can send HR Master Data thru PFAL.
yes you can send the Pernrs as they are Components of Organizational Elements.
Here is the Procedure to send Personal Numbers:
1.Execute the transaction PFAL.
2.Give the object type as P.
3.Give the Pernr values in Object ID field
4.Select the transfer mode as Update
5.In the Receiving Partner give your receiver name
6.Give the message type as HRMD_A in the Message Type field.
7.Dont change the remaining values.Keep it as such.
8.Execute the Program.
Also keep in mind that while sending the HR data you need to follow the certain sequence
unless otherwise your data wont be replicated successfully.
Here is the sequence O,S,P and C.
Means before sending P you should send O and S.
Cheers,
Abdul Hakim
Mark all useful answers..

Mail triggering through NACE transaction.

Hi all,
I have a requirement of triggering mail when BOM(CS01) is created on SAVE save event.
Can any body tell me if it is possible through NACE transaction.(I need to add some more conditions also) and if yes how to do it.
Thank you.

Hi,
Check the below link which is of similar kind of requirement.
RFQ mail sending
Thanks,
Asit Purbey.

IDoc to IDoc through ALE

hello experts !! could u plz give me some idea or step by step help for creating IDoc to IDoc data transfer through ALE.
My scenarion is like the following:
there will be two client in two R/3 system..(Sending and receiving)....
in sending system i want to insert data in a particular table....
that data will be automatically updated in receiving system..
plz help meeeeeeee
thanks...
points will be rewarded.......

Hi Soumya,
Follow the process as below
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards,
Satish

Problem in processing incoming IDOC

Hi All,
I have a problem while processing Incoming IDOC in the system.
While I try to process and FI IDOC (without purchase order) in the system, by giving the appropriate GL account and cost centre where the document should get posted to (in transaction WE19), I find that the system creates the IDOC successfully with status 53. However, it creates a parked document in the system for the vendor.
When I try to post the document through transaction FBV0, the system asks for a cost centre. Can you please clarify, why the system is asking for a cost object though it is given in WE19 transaction. Ideally while processing the IDOC the system should post the document directly as it has all the relevant details in the IDOC right?
(Just for info, I have given the GL account details in segment E1EDP19 with qualifier 002 and the cost centre in segment E1EDP30 with qualifier 045)
Expecting your help in this regard.
Regards
Nagarajan N

Hi
You can use WE19 to debug the Idoc FM.
Check this link if it is helpful:
Debugging Idocs
Regards
Neha

Reg : change pointer mechanism for triggering the IDOC for delivery note

Hi ,
I am working on a change pointer mechanism for triggering the IDOC for delivery note and will be using this message class DESADV.
So SAP has suggested for assigning the message class DESADV with the function module in MASTERIDOC_CREATE_SMD_DESADV in BD60 transaction code.
So I was looking to create this MASTERIDOC_CREATE_SMD_DESADV function module in SAP and SAP suggesting that we should create this MASTERIDOC_CREATE_SMD_DESADV function module as same as the function module MASTERIDOC_CREATE_SMD_MATMAS.
So do anyone knows that is there any tool has been provided by SAP for creating this function module MASTERIDOC_CREATE_SMD_DESADV in SAP system for triggering the change pointer mechanism for outbound Delivery.
Thanks !
Regards,
Kiran

Hi,
When you are change pointer the system itself will take care of sending the changed master data to your partner system and the user will not have any intervention. If you really wanted to have that then you need to use the change pointers to read the master data which is modified in a custom program and then display that on the screen. Once the user selects that master data records then trigger an IDOC for creating the idoc for that master data and also flag that master data record as processed in the SAP BDCPS standard table, so that the same record will not be picked. If you wanted to know how the change pointers piece of code is written go through the program RBDMIDOC and you can understand how the change pointers logic is written.
Thanks,
Mahesh.

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

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.

Problem while creating INVOIC idoc

Dear All,
I am facing a error messege while creating INVOIC(using MIRO transaction) idoc through EDI for a partner(vendor).
In MIRO transaction after selecting one Item I clicked GoTo>Messege>Item
Then I selected output type (Z output type) , Medium EDI, Function VN ,Partner number (say 123) language EN.
After that when I presse enter I am geting a messege "Partner 123 does not exist for partner function LF".
All the configuration is done including partner profile for 123(partner type is LI).
Please let me know what is the reason for this error. Do i need to make any changes in configuration?
Regards
Arindam

Go to BD54 and maintain table view for ur partner type
hope this helps u..
Thanks,
Anil
Edited by: anil sasidharan on Apr 17, 2009 11:42 AM

Problem in triggering MATMAS IDOC through BD10 transaction

Similar Messages

Maybe you are looking for