Point Changer sometimes don't generate IDoc MATMAS

Hello,
I have activated Point Changer for MATMAS and when I change material sometimes the IDoc is generated and sometimes is not.
In the table BDCP2 I show the change but PROCESS field is not X(so hasn't be processed). That also happens when I create a Material.
Could it be because in some materials I don't have, Plant, Sales organization, division?
If I run transaction BD40 for the group of materials, all these IDocs are generated. I check all the filters but I didn't see any. I need all the IDocs are generated always.
Any idea how?
Thank you

Hi,
not for all fields change pointer is activated. Go to se11 for MARA or other material relevant table which contains the fields you are looking for. Double click on data elements and go to tab further characteristic. The flag Change Document should be set for the field.

Similar Messages

Material master/Output type IDOC /MATMAS

Hello ,
I want to generate Idoc(MATMAS) whenever a material is created or changed. I could do the same for ME21N/ME22N for PO with PO idoc. Would like to know whether there is output types for material master or anything else so that i can generate Idoc for my senario.
Thanks for ur time.
Jeeva.

Hi,
the configurations which we do for material master is below...we don't give any output for material master,becoz its a master data not transactional data..
        For distributing master data like material master, vendor master, customer master we have standard transaction codes that are provided by sap.
Bd10(send material master)
Bd12(send customer master)
Bd14(send vendor master)
Bd30(boms)
The order of Tcodes are:
           Bd54 (creating logical systems)
           Scc4 (assigning logical systems )
           Sm59 (rfc destination)
           We81 ( message type)
           We30 ( idoc type)
           We31 ( segment type)
           We82 (linking message type and idoc type)
           We21 (creating port)
           We20 (partner profiles)
           Bd64 (Distribution model)
           Bd10 (material master)
Ex: material master.
     Message type: matmas.
     Idoc type: matmas05.
Rewrad if helpful.
Regards,
Nagaraj

How i need to write a logic to generate idoc for some of infotypes, when i change the single infotype

Hi experts,
I have an requirement , when I change any infotype record from pa30 or pa40, i.e
suppose I am changing the infotype 0002 in pa30 , the idoc only generated for that changed infotype only,
but I need it to generate the idoc for some other infotypes also I.e(0000,0002,t528t, 0016).
So please give me some help to generate idoc when I run a rbdmidoc(bd21).
Thanks in advance.
Venkat

yes, visible bounds is reading the non-visible masked objects too.
you're going to have to do it the hard way, loop through all your objects to get your bounds manually, and while you're at it, test for clipping masks and use the masking path instead.

Why does my mouse pointer change from a hand to a downward facing arrow sometimes?

why does my mouse pointer change from a hand to a downward facing arrow sometimes?

the-edmeister, you are a genious. I went to "view" then "toolbars" and de-selected "yahoo toolbar" and then moved the curser over my firefox page and it now works completely including the problem area (the top 3 cm of each screen). Thank you, thank you, thank you, thank you, thank you, thank you. You have no idea how good I feel know on this otherwise cold, windy and rainy day.

Generate IDoc from MM02 automatically !

Hi All,
I have gone through many posts, but could find a way where i could generate an IDoc and Dispatch it the moment a Material is saved after changes being done. There is ofcourse a way i.e. to schedule RBDMIDOC in the background at regular intervals. But my requirement is to dispatch the IDoc immediately once the changes have been done.
Is there any way to achieve this ?.
Regards,
Chaitanya.

Hello Chaitanya,
Have a look at transaction BD10. The program is RBDSEMAT and it is well documented.
In ALE configuration, in the partner profile settings, there is a radio button under "Output Mode" named "Transfer IDoc Immed.". If you select that option then it will be sent immediately when BD10 is run for the logical system in question.
But to answer your question specifically, to create and send the IDoc when the Save button is hit on Material Master Create/Change screen - I don't think there is a direct way to achieve this...only way I can think of is to submit the BD10 program with the single Material no. that is being created/changed within one of the user-exits/BADIs behind the Mat Master. Then again, you'll have problem when in Create mode because SAP won't generate the new Material No. till the very end, so it depends at which point the user-exit is called.
So in summary, I'd suggest not to submit BD10 via any user-exit but to schedule BD10 in the background every 15/30 mins with partner profile radio setting "Transfer Immed." for the logical system it is attached to so that all mat master changes are replicated frequently, which I believe is the purpose of BD10.
Hope this helps,
Cheers,
Sougata.

Change pointers to trigger the IDOC

HI
I am having a selection screen with fields to create a custom info record (transaction VD51/ VD52 )
Customer
material
salesorganisation
distribution channel
division
if we can use change pointers to determine when procedure is triggered.
Please provide the steps for that (including change document)or we need to check the CDHDR table using the following fields.
Plz suggest

Change pointers is the one of the IDOC processing method in ALE.
In this once we make the config to any of messages type , if any changes are made in sending system then IDOC will be posted directly to destination with user interation.
Changes pointers are configured using BD50,BD51,BD53,BD61.
Change pointers are stored in tables BDCP and BDCPS (or BDCP2 in case of high-performance setting) - like CDHDR and CDPOS for change documents (but this is not a controlling table!).
1. Do you really need change pointers?
You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
You can deactivate change pointers and activate them again with the transaction BD61.
2. Do you really need to activate change pointers for this messages type?
If some messages types are no longer to be distributed by change pointers, you can
deactivate change pointers for this message type.
You can deactivate change pointers for the message type
and reactivate them again in transaction BD50.
For reduced message types, deactivate the change pointer with the
Reduction tool (transaction BD53).
Applications which write change documents will also try to write change pointers for ALE operations. These are log entries to remember all modified data records relevant for ALE.
Most applications write change documents. These are primarily log entries in the
tables CDHDR and CDPOS.
Change documents remember the modified fields made to the database by an
application. They also remember the user name and the time when the modification
took place.
The decision whether a field modification is relevant for a change document is
triggered by a flag of the modified fields data element. You can set the flag with
SE11 by modifying the data element.
For the purpose of distributing data via ALE to other systems, you may want to
choose other fields, which shall be regarded relevant for triggering a distribution.
Therefore R/3 introduced the concept of change pointers, which are nothing else
than a second log file specially designed for writing the change pointers which are
meant to trigger IDoc distribution via ALE.
So the change pointers will remember the key of the document every time when a
relevant field has changed.
Change pointers are then evaluated by an ABAP which calls the IDoc creation, for
every modified document found in the change pointers.
The Change pointers are written from the routine CHANGEDOCUMENT_CLOSE
when saving the generated change document. So change pointers are automatically
written when a relevant document changes.
The following function is called from within CHANGEDOCUMENT_CLOSE in order to write the change pointers.
CALL FUNCTION 'CHANGE_POINTERS_CREATE'
EXPORTING
change_document_header = cdhdr
TABLES
change_document_position = ins_cdpos.
Activation of change pointer update :
Change pointers are log entries to table BDCP which are written every time a transaction modifies certain fields. The change pointers are designed for ALE distribution and written by the function CHANGE_DOCUMENT_CLOSE.
Change pointers are written for use with ALE. There are ABAPs like RBDMIDOC
which can read the change pointers and trigger an IDoc for ALE distribution.
The change pointers are mainly the same as change documents. They however can
be set up differently, so fields which trigger change documents are not necessarily
the same that cause change pointers to be written.
In order to work with change pointers there are two steps to be performed
1) Turn on change pointer update generally
2) Decide which message types shall be included for change pointer update
R3 allows to activate or deactivate the change pointer update. For this purpose it
maintains a table TBDA1. The decision whether the change pointer update is active
is done with a Function Ale_Component_Check
This check does nothing else than to check, if this table has an entry or not. If there is an entry in TBDA1, the ALE change pointers are generally active. If this table is empty, change pointers are turned off for everybody and everything, regardless of the other settings.
The two points read like you had the choice between turning it on generally or
selectively. This is not the case: you always turn them on selectively. The switch to
turn on generally is meant to activate or deactivate the whole mechanism.
The change pointers which have not been processed yet, can be read with a function
module.
Call Function 'CHANGE_POINTERS_READ'
The ABAP RBDMIDOC will process all open change pointers and distribute the
matching IDocs.
When you want to send out an IDoc unconditionally every time a transaction
updates, you better use the workflow from the change documents.
Reward if useful

Generate idoc from Transaction

Hi,
What are the settings/configurations need to be done in ECC 5.0 for generating an idoc from a transaction. I am executing a transaction C202 for changing BOM
Thanks

Hello,
BOM is a master data. The technique mostly used to send master data is via Change Pointers wherein for any changes taking place in the master data, change pointers are written in the change pointer table (table BDCP).
A program (RBDMIDOC) has to be scheduled in background which reads the change pointers and sends the IDOC to the destination system.
Also for BOM transaction BD30 can be used to send BOMs to destination logical system.
The technique for generating an idoc from transaction is called mesage control (or output control). It is valid for transaction documents (like sales order, purchase order etc).
Hope this helps.
Regards,
Gajendra.

Message type for generating IDOC for SUBCONTRACTING PURCHASE ORDER

Hi All,
I have to generate IDOC for PO creation or change .
I am using IDOC_OUTPUT_ORDERS and IDOC_OUTPUT_ORDCHG.
The messagetype.idoctype I am using is ORDERS. ORDERS05 and ORDCHG. ORDERS05.
Now the confusion is regarding whether this message type will work in case of SUBCONTRACTING PURCHASE ORDER as well ?
As I have gone through some websites and came to know that I will have to use PORDCR1.PORDCR102 specially for subcontracting.
And programs we need to use is BUS2012_ICH_R3 instead of RSNASTED and Form Routine SEND_PORDCR1 instead of EDI_PROCESSING.
Purchase Order Collaboration scenario - Not generating IDOC in ECC
http://www.erpgenie.com/faq/edi_purchasing.htm on this site question no 8.
Subcontract PO IDOCs
I hope your experience will help me .
Please reply ASAP.
Edited by: uttam27 on Dec 4, 2011 1:47 PM

There is a generic function to create change pointers for all message typs - 'CHANGE_POINTERS_CREATE_DIRECT'. This is triggered only if you configure your message type to create change pointers from BD50.
Once you activate it do any change to orders you can see change pointer tables BDCPV filled. Then BD21 will read the changes and generated outbound idocs accordingly.

Problem with "Confirmation" changes in PO using ORDRSP Idoc

Hi all,
I have an issue when changing "Confirmations" tab in PO.
I configured Output Message Z001 that should be determined when I change values in that tab. That scenario is working fine, but the real change will be done by ORDRSP Idoc. Using that Idoc, change is done in the PO but no output message is determined (condition records are fine). I need to send a Custom Idoc once that change is done so I need to determine the output message.
I searched for an OSS note, as it should work using Idoc process, but I didn't found anything. Does anyone know if it exist?
Thanks in advance for your help.
Regards.
David.

Thanks for your answer Jelena,
The main problem here is that all the flow works fine if I execute if manually:
Change in "Confirmations" tab is done --> output message Z001 is generated --> Custom Idoc Z is created.
Therefore, WE20 is correctly configured and also all the required fields that can be changed in "Confirmations" section.
The problem is that real scenario should modify that values using ORDRSP inbound Idoc (ORDERS05). That Idoc is changing the PO, but that change is not triggering any output message (although the same change did it manually), so custom Idoc Z is not created.
Maybe I didn't explain myself very well in my previous message.
Thanks & Regards,
David.

Extension of generated Idocs types

hello,
does anybody knows why I can not create extension of generated (means in table EDBAS-GENERATED = 'X') idocs?
I tried to extend idoc BATMAS03 on R/3 Ecc 6 and got message:
message e099(b1) with
'Action is not possible for generated idoctypes'
In former version of R/3 4.6C it was possible to extend such IDoc BATMAS02 (generated one) without any problems.
Of course I found in program MSED5F02 in routine CREATE_EXT_STRUCTURE new (in comparison to 4.6C) extra check which protects against extension of generated IDocs, but I want to get to know what was behind that decision or how to workaround that problem.
Thanks in advance,
Marcin

Hi,
User Exits are used to populate data in new segments added and to read them
back which provides extension to existing idocs.
IDOC EXTENSIONS
SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type. Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
First, determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save. Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
Pls reward helpful points.
Regards,
Ameet

Error when generating IDoc from MC document - workitem to all the SAP users

A workflow item with the subject of Error when generating IDoc from MC document is sent to all the SAP users' inbox. Is it possible to stop the generation of this work item? If that is not possible, can we limit sending the work item to a specific user/agent instead of all the users in the system?
It appears that these work item or error message are generated when one of the developers reopen the POs and add line items. Moreover, during that time the procurement team blocked the IDOCs from going out to the vendors when changing and resaving the POs. Therefore, we need stop the generation of error message/work item when the IDOCs generation blocked.

Please check Rule 70000141which is the default rule for this task. Inside this rule a FM is attcahed which is reading table EDO13 and EDPP1 where agent is retrieved Probably this table entries are not maintained. This Workflow is getting triggered from Message cOntrol I think.
Please check this link for
http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4aec8453d11d189430000e829fbbd/frameset.htm
<b>Reward points if useful and close thread if resolved</b>

Generate IDoc COND_A01

Hi all,
I need to generate an Idoc with type COND_A01. Does anyone have some insight on how can I do this?
Please note that I don't want to use WE19, because what I need to do is to get some "real" data from the system and check what values go into which fields.
Thks

Hi Bruno,
Welcome to SDN.
You may need to ask SD Functional folk to create new pricing report (t/code V/LA) with sending IDoc, message type and logical system paramaters available for input.
or you can copy an existing pricing report (t/code V/LD) into custom report/program and change below parameters to be displayed.
PARAMETERS sen_idoc(1) TYPE c *NO-DISPLAY.
PARAMETERS p_mestyp LIKE tbdme-mestyp *NO-DISPLAY.
PARAMETERS p_logsys LIKE tbdls-logsys *NO-DISPLAY.
Once the report is available for you then the next step is to configure ALE and partner profile in order to generate IDoc COND_A01 from the pricing report.
Hope this will help.
Regards,
Ferry Lianto

Passing Changed extended fields using ALE-IDOC to receiving system

Hi all,
Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
For ex. in matmas05 extended for classification and inspection view and then created using 'CREATION'
related bapi.Do i also need to incorporate the changes by change related bapi or ir can be handled by change pointer concept.
Thanks.

Hi Sanu
1) Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.
=> Looks like you have extended standard IDOC here. so you need to find User Exit or BADI for the Push program to populate the additional fields. Yes, it is possible thru change pointers as well.
1) Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
=> Yes, as suggested in 1 try finding User Exits/BADIs.
Regards
Shital

File to IDOC:how do i relate inbound idoc with generated idoc in the R/3

hi experts;
can any body tell me how can i relate the IDOC number genrated in the PI with the generated IDoc number in the SAP R/3 system for file to IDOC scenario?
in SAP PI for tcade idx5, idoc no is:12002
but in SAP R/3 in tcode WE05, idoc no is:846915
how can i know a particular message (in SAP PI) created a particular idoc in the backend SAP R/3 System.
thanks in advance,
kumar

Hi Kumar
at the time of testing you have to note down a time at what ur file got picked up ok
then go to we05
-> give the date on CREATED ON field.
-> then in BASIC TYPE field select your particular IDOC CREMAS05 or whatever, see the TIME field that you have noted down at the time of testing, if that is matching means that is ur latest IDOC you have tested.
-> one more thing, tha last IDOC showing in the list means that is your latest IDOC you have tested.
Hope i have helped you, points plz
Warm Regards
Dheeraj Kumar

Not generating IDOC for payment Advice to Vendors

Hi,
IDOC was getting generated before one month but now SAP system has stopped generating IDOC for vendor Payment advice. This problem is with all the vendors.
After execution of t-c-ode F110, payment document is successfully created, but IDOC is not geenerated. There is no log about "IDOC not getting generated"
Checked Table REGUH, IDOC number is displayed as 0000000000000.
This was happening perfectly one month back.
There is no change in Vendor master data, IDOC number range is available.
There is no posting of IDOC in table DFKKTHP and checked Report REREMITADV for which there is no data.
Waiting for your valuable responses.
Regards
veleyudham

Hi,
First check certain customization:-
(1) FBZP setup for payment method at country level. Whether IDOC generation program is assigned or not.
(2) Then check the variant of RFFOEDI1 in the printout tab of F110. Is the selection creteria OK?
(3) Check the partner profile in WE20 for the bank.
Then run the program RFFOEDI1 in SE38 for your payment run and check the output.
You can also get this program debugged from you ABAPer to have root cause analysis.
Regards,
Gaurav

Point Changer sometimes don't generate IDoc MATMAS

Similar Messages

Maybe you are looking for