RBDMIDOC or RBDSEMAT for MATMAS ?

Hi All,
I have to create matmas05 idoc whenever material create or change using MM01/MM02 .I have configured all the settings for change pointers. Now I have to create a job to run periodically . my question is which program should I use to schedule job for my interface. RBDMIDOC or RBDSEMAT ?
I knew that RBDMIDOC for change pointers and RBDSEMAT to create IDOC .
Please clarify.
Thanks - Vinay

Yes you can.
RBDMIDOC is used to process ale changepointers (look at table BDCP/V/S).
A new entry is made in the tables if you create MM01 or change MM02 a materia.
With this job you send all changes (mm01 or/and mm02) to all receivers in the distribution model (look at bd64 tcode)
If you need to send a "full/initial load" or "single items" to ONE specific receiver, than you have to use the BD10 (RBDSEMAT) tcode.
Regards,
Gordon

Similar Messages

RBDSEMAT or RBDMIDOC for MATMAS IDoc ?

Hi,
I have to create an IDoc when material create or change using MM01/MM02.
I made all the necessary settings to create an IDoc . But which program should I use to generate an IDOC ?
RBDSEMAT ( BD10 ) or RBDMIDOC ( BD21) ?
Thanks - Vinay.

RBDSEMAT- Stand alone program to generate IDocs (Send Material)
RBDMIDOC - Outbound triggered from change pointer
You can use standard program RBDSEMAT (BD10) to send IDoc for particular material by specifying material number only.
RBDMIDOC is used for creating IDOCs based on change pointers. RBDMIDOC is usually automatically executed in the background...

Difference between RBDMIDOC and RBDSEMAT

Hi Guru's,
I have a problem regarding different segements in the MATMAS IDOC. When I run RBDMIDOC with a message type, it will look in the change pointer table and process the MATMAS IDOCS, when I look at some of the idocs I see for example segments missing like E1MARCM or E1MVKEM. when I take the same material nr and process it via RBDSEMAT and providing the same message type I do get the E1MARCM and E1MVKEM segments.
Can someone explain why this is happening?
Best regards,
Guido Koopmann

I have been reading sap help on this topic: http://help.sap.com/saphelp_45b/helpdata/en/78/2178da51ce11d189570000e829fbbd/content.htm
If I understand it correctly there is way to set some segments to mandatory MSGFN 018, but where is that done?
Best regards,
Guido Koopmann

Problem with RBDMIDOC in executing for diff logical systems

Hi ALL,
We are using message type HRMD_A and we have configured two logical systems using that message.So when we execute RBDMIDOC to generate idoc for change pointers it triggers idocs to both the logical system which we dont want.Is there any other program apart PFAL which does the same job of RBDMIDOC and we can give logical system as input parameter
Thanks
Bala Duvvuri

Vijay,
we cannot have the scenario which I mentioned unless we develop a custom program from scratch that accepts logical system as input parameter
Thanks
Bala Duvvuri

No Communication IDOC generating for MATMAS --- Urgent

Hi,
I have two systems in the Landscape; one is DA1 and other is DA3. Both systems are exactly identical.
When I am triggering idoc of message type MATMAS from bd10 in DA1 systems, it successfully generating MATMAS idoc and I am able to see that idoc in we02 but when I am triggering MATMAS idoc in DA3 system; it is generating Master IDOC but it is not generating Communication idoc for Message type MATMAS and in we02 as well I am not able to see any such idoc.
Both the Systems are exactly same and I have checked ALE configurations in both the systems, they are same.
Can anyone suggest, what could be the problem.
Regards,
Varun

hi,
As Bineah mentioned check the distribution model, distribute it and generate partner profile. verify all the configurations once again i hope it will do.
if any queries let me know .
~linganna

Reprocessing change pointers for MATMAS idoc

Hi
I have a situation where i executed BD21 for changes to materials but no idocs were created due to some issue with the distribution model. Now i have fixed the issue and would like to re process all the materials which were changed. Since i have already executed BD21, now no new idocs are being generated. Is there a way to reprocess the changed materials and generate the idocs again.
Thanks
Nag

Hi Roger
Thanks for your inputs. I am trying to generate idocs through the change pointers and not using output determination.
When i executed BD21 the first time, idocs were not generated due to some config issues. But the job ended successfully saying that idocs were generated and marked all the changed material documents under change pointers (But in WE02, the idocs never showed up actually).
Now i have fixed the issue in config and want to generate the idocs using the change pointers. Is there any way to regenerate the same idocs using BD21 or some alternative.
Thanks
Nag

Generating an idocxml file for matmas idoc,getting invalid characters in it

HI
i am generating and(ZMATMAS) idoc xml in a folder in R3 using the Port (No PI involve here). and after generating the file SAP PI system will pick that file to process , but for some files,invalid characters like oxb(vertical tab) are being passed due to which messages are failing in PI ,SO HOW I CAN AVOID GENERATING THESE INVALID CHARACTERS inxml file in R3.
regards
sandeep
Edited by: pendyalas on Feb 2, 2011 10:48 PM

>
pendyalas wrote:
> Thank you , . i have one more concern how to type the invalid character ((0xb )vertical tab) while declaring them in table in we21
>
check out also the following SDN thread and OSS Note,
Handling of 0xb character
Google to find out how special characters can be entered.. There were some suggestions to press ALT and enter the four digit representation for the special characters (you can probably play around with it)...

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.

Long runtime of RBDMIDOC for IDoc ARTMAS

Hi,
   We are in IS Retail. We are using IDoc to capture article master creation & changes, and to reflect those details in retail stores. For this we have created custom Z message type & assigned it to a sap standard basic idoc type ARTMAS05. We have also activated the change pointer ARTMAS. There s no issue in IDoc generation. But when we run the program RBDMIDOC for Idoc generation, it is taking hours together for execution.
   I could not find any sap note for performance improvement, whereas for MATMAS there are performance notes 863744.
   Is there any solution for runtime / performance improvement for RBDMIDOC, for idoc type ARTMAS ?
regards,
Nagarajan.J

Hi,
I am also having the similar requirement but only problem is when i try to create idoc through BD21 system is creating idoc of message type ARTMAS although I have defined bespoke message type,
can you please tell me if in your case bespoke message type is being selected for creating idoc if yes then please let me know which config I may be missing.
Thanks in advance for your help.
Cheers
Ashutosh

Performance improvement for ALE/IDOC processing

Dear experts,
Could you let me know any information to tune performance?
In our system (SAP R/3 Enterprise 6.20), material master data is distributed from one client to other clients in the same instance. It is because material master is maintained centrally, and is distributed to other clients for member companies.
During the night batch, distributing master data takes more than 2 hours. Although the distribution usually finishes without errors, we would like to explore ways to improve processing performance. Especially, program RBDMIDOC runs long time to create IDOC for MATMAS, even 0 master IDOC is set eventually.
OSS notes of the list for OS/DB/SAP parameters related to ALE/IDOC, tips in organizing batch jobs, etc, will be very appreciated.
Many Thanks,
Nori

I'd recommend to profile the program at least once to see where there's possible room for improvements. I.e. an ABAP runtime analysis and SQL trace would be good for a start. You can check out the links in thread Please Read before Posting in the Performance and Tuning Forum, which will give you some references if you need them. Once you have more details, you either know what you need to do or you can provide them and ask a more specific question (and thus you will receive much better answers).
As a general remark though I've seen often poor performance initially on the changer pointer selection, because there are too many entries in the table (due to system generating unnecessary change pointers, which should be disabled or/and lack of proper reorganization, i.e. deletion of old/processed change pointers via BD22). Sounds like this is most likely also the cause of your problem, because otherwise it's hard to explain long run times without generating any master IDocs. You can check the number of change pointers easily via view BDCPV or BDCP2 - it depends how you store your change pointers (most likely you find them via view BDCPV in a 6.20 system, unless somebody switched it to the newer BDCP2).
If you still have them in BDCPV (or the underlying tables to be more precise), check out [OSS note 305462 - MOD: Migration change pointer to table BDCP2|https://service.sap.com/sap/support/notes/305462], which will provide you a general hint how to do that (and thus also improve the performance). However, if you're currently not deleting any old change pointers, you should ensure that a regular job runs for transaction BD22 (program RBDCPCLR). You'll easily find other (possibly relevant) OSS notes by doing a search yourself...

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.

What is Ale, Edi,IDoc tech for sap

Hi all,
What is Ale, Edi,IDoc tech for sap?
Thanks.

hi deniz,
ALE
ALE
Triggering OB via Change Pointers:
 When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
Outbound Process:
When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
 To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
Asynchronous Communication:
The data that is IDocs and the function module are stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
Inbound Process:
The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
 Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
In the table TBD51 there will be entries to find which option is used.
Transactions:
SALE - IMG ALE Configuration root
 WE20 - Manually maintain partner profiles
 BD64 - Maintain customer distribution model
 BD71 - Distribute customer distribution model
 SM59 - Create RFC Destinations
 BDM5 - Consistency check (Transaction scenarios)
 BD82 Generate Partner Profiles
 BD61 Activate Change Pointers - Globally
 BD50 Activate Change Pointer for Msg Type
 BD52 Activate change pointer per change.doc object
 BD59 Allocation object type -> IDOC type
 BD56 Maintain IDOC Segment Filters
 BD53 Reduction of Message Types
 BD21 Select Change Pointer
 BD87 Status Monitor for ALE Messages
 SALE Display ALE Customizing WEDI - ALE IDoc Administration
 WE60 - IDoc documentation
 SARA - IDoc archiving (Object type IDOC)
 WE47 - IDoc status maintenance
 WE07 - IDoc statistics
BALE - ALE Distribution Administration
 WE05 - IDoc overview
 BD87 - Inbound IDoc reprocessing
 BD88 - Outbound IDoc reprocessing
 BDM2 - IDoc Trace
 BDM7 - IDoc Audit Analysis
 BD21 - Create IDocs from change pointers
 SM58 - Schedule RFC Failures
EDI
EDI(Electronic Data Interchange )
RFC DESTINATION:
 A logical name used to identify the remote system on which a function needs to be executed.
Partner Profile:
 It defines the characteristics of data being exchanged with the business partner.
Partner Function:
 Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
Partner type:
 The type of your business partner .
 EDI KU/LI
 ALE -- LS.
Archiving:
 -Need to archive the important transmitted document
-Created in SARA
 -Assigned in WE20.
PartnerProfile Tips:
 RSECHK07- Consistency check for Partner Profile.
 If you want to modify partner profile; copy it and then modify. If you cant modify it , u have to delete it.
 To move partner profile to production system choose Partner -> Transport
Port defintion:
 It defines the medium through which data is exchanged between systems.
 tRFC - Used by ALE
 FILe - Used by EDI
 R/2 system system port For R/2 system
 Internet port - to connect with internet applications
 It also depends on the receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
Startrfc - Program to execute RFC enabled Fun.mod. in SAP
EDI_DATA_INCOMING - To send data as inbound
EDI_STATUS_INCOMING - To send status to SAP
RSPARAM - To know the gateway service of the SAP system.
Message Control:
 Output controller
 A service program for determining the output type
 To generate and manage various outputs from an application and control their medium and timing of exchange.
 To retransmit the document without duplicating it
Procedure:
 A procedure defines a set of possible outputs for an application
 There may be more than one procedure but only one can be active
 Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
Output type:
Defines the characteristics and attributes of the output.
Access Sequence :
Defines a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
Sapfans Q & A
SREL_GET_NEXT_RELATIONS -
Function Module that will provide me the number of the document that was created by an IDoc
RLSUB020
Program which uses the above function module.
Upgradation problem
When the old version program is upgraded in to newer version(4.0b  4.6c) the SE38 editor wont allow u get thru the programs normally to get rid of this.
Solution:
EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
this fixes the links
ALE( Application Link Enabling )
Disk Mirroring:
Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disks contents.
Replicas:
Maintaining redundant data across multiple systems.
ALE:
It provides distributed environment to integrate non-SAP systems
Provides guaranteed delivery of data regardless of network problem to application.
Logical system :
 The systems involved in distributed environment are assigned a logical name which uniquely identifies a system in a distributed environment.
Data Mapping:
 Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
Message Types:
 Represents a business function
 Technical structure is the IDoc type
 Or can say an instance of IDoc.
IDoc :
 They are containers used to exchange data between any two process.
 It represents an IDoc type and IDoc data
 IDoc type is structure and IDoc data is an instance of it.
Pls reward if helpful.

Creation of New Message Type for Extended IDoc

Dear Friends,
I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
for Change Pointers.
Warm Regards,
Naveen Mutyapu.

Hi naveen mutyapu,
see these links
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
happy learning.
thanks
karthik

Sending step in Integration Process waiting for Acknowledgement infinitely

In process I had to send an MATMAS, CLFMAS and CNPMAS. The data for
this IDoc comes in one message from third party system. So, my
Integration Process has receive step (to collect a data), and three
send-steps (for MATMAS, for CLFMAS, for CNPMAS), one by one. The
receive-step catch an inbound message and then (without transforms)
send this message to each of this three send-steps in Asynchronous
mode. The inbound message transforms in Interface Determination to
IDoc. Three steps, one Interface Determination with three conditions,
that looks
like «ProcessStep=send_matmas», «ProcessStep=send_clfmas», «ProcessStep=s
end_cnpmas», and in this place I set a mapping to transform inbound
message to IDoc. All send-steps has property Acknowledgement, which set
to Transport value. So in first send-step MATMAS goes to R3, then R3 in
response send ALEAUD IDoc (trans WE05 shows an incoming MATMAS and
outgoing ALEAUD); ALEAUD comes to XI (trans IDX5 shows inbound and
outbound messages), but ALEAUD didnu2019t transforms to XI Acknowledgement.
And there is no any CLFMAS or CNPMAS, because all processes sleeps in
their first send-steps (trans SWWL shows a many STARTED processes).
Each send-step waits for event u2018SEND_OK_TRANSPORTu2019. Moreover, if I use
trans sxmb_moni to monitor this situation and if I press refresh (F5
button) every time, sxmb_moni every time requests a status of
Acknowledgements, XI transform ALEAUD to Ack, send-step in process
catch this status, process wake up and moves to next send-step (which
sends an CLFMAS and waits for Ack). By continuously pressing refresh
(F5) in sxmb_moni all process becomes COMPLETED (trans SWWL), all
ALEAUD transforms to XI Ack and all IDocs goes to R3. But pressing F5
itu2019s not a solution for integration.

Hi Igor,
I dont think your manual refresh changes the status . The status changes is the status change of GUI . The system will take how much so ever it needs to take and not as per your manual refresh.
Regards
joel

Error handling for inbound function module

Dear all,
I have written my custom function module for matmas idoc extention.In the begining of function module i have used IDOC_INPUT_MATMAS01 and then have coded my BDC.For handling errors in caese BDC fails i am filling table idoc_status. wih status 51.
But this gives eror as-
Status records with status 51 after status 53
Message no. B1357
Diagnosis
The application function module controlling the ALE inbound processing has passed several status records to ALE. The status of the last of these was '51'. Before this, a status of '53' was passed.
Procedure
If you have written the application function module yourself, you need to change the program.
Can anybody guide me how to get the exact application errors in Application log.
Thank you.

Hi,
You are using BDC after the FM 'IDOC_INPUT_MATMAS01'. Right??.... The problem is, The function Module IDOC_INPUT_MATMAS01 itself posts the material and set the status '53' i.e. document posted. You can not have any error status '51' after that.
I don't understand the need of BDC in spite of the FM 'IDOC_INPUT_MATMAS01'. But if whatever the reason, you still want to use the BDC and set the status to 51, After the FM 'IDOC_INPUT_MATMAS01' call, Delete status table where status = '53'. and then proceed for the BDC...

RBDMIDOC or RBDSEMAT for MATMAS ?

Similar Messages

Maybe you are looking for