Outbound IDOC not getting triggered while new master data is created

Hi Experts,
I am trying to trigger an outbound idoc for Cost Center master data when ever cost center is being created or cost center is being changed. (Usinf COSMAS)
I have successfully made use of change pointers and now able to trigger the idoc when ever Cost Center is getting changed. But while creating new Cost center, IDOC is not getting triggered.
I used the function module MASTERIDOC_CREATE_SMD_COSMAS for triggering the idoc.
Could one of you please let me what would have gone wrong? Since IDOC is getting triggered while changing the master data but not getting triggered while creating new master data.
Thanks in Advance,
Vinoth

Hello,
when you activate BD21 for a message type, it creates a entry in the SAP tables. that these Cost Centers have been sent already and any susequent changes to this will trigger a IDoc.
As for BD16, scheduling it wont help as, you need to specify the selection criteria, and i do not see how you will be able to dynamically get the selection criteria.
Try BD95, and BD59 to create a change pointer for a field, so when ever this fields is modified (new/updated) an idoc will be triggered.
regards,
Abhishek

Similar Messages

Outbound idoc not getting triggered

Hello,
After recieving the Advanced Shipping notification from the vendor an inbound DESADV Idoc is generated and due to which an outbound PORDCH Idoc with the information of the affiliated PO Nr. and VAT Code should be triggered. But, it is not happening! Please help and tell me which settings needs to be checked.

Hello,
when you activate BD21 for a message type, it creates a entry in the SAP tables. that these Cost Centers have been sent already and any susequent changes to this will trigger a IDoc.
As for BD16, scheduling it wont help as, you need to specify the selection criteria, and i do not see how you will be able to dynamically get the selection criteria.
Try BD95, and BD59 to create a change pointer for a field, so when ever this fields is modified (new/updated) an idoc will be triggered.
regards,
Abhishek

Profit Center not getting copied from WBS master data to settlement rule

Hello,
I am facing issues during settlement to G/L. From FI side we have set up some validations that the FI postings shld always carry a Profit Ctr. Now when I am doing settlement to B/S account, the profit ctr from WBS master data gets copied to settlement details and hence on FI posting (Credit line).
However when I am trying to settle to Expenxse/P&L account this is not happening. The profit Ctr is not getting copied from WBS master data to Settlement details and hence the settlement is not going thru. The profit derived is a dummy profit ctr and not the one on WBS master data.
I have posted this query on FI forum too but no satisfactory answers.
Pls let me know, what is the system behaviour....will the prof ctr on WBS master data gets copied on settlement rule details automatically ?
Sarang

Which exit do I use in OPSN? any thts or some exit in FI?
I am on ECC-6.0...
One thing to mention, the prof ctr is getting copied to settlement rules for Balance sheet account but not for P&L.This is more confusing...
Sarang

IDOC not getting triggered

Im triggering an idoc IDOC_OUTPUT_ORDERS immediately when i create/change the PO
However the idoc is getting generated when i change only certain fields.
When i change other fields it does not get triggered.
Why?
-Dexter

Hi Dexter,
I hope these links might be useful to you.. refer all the links, you will get it..
Idocs trigering
Idocs Triggering!
regarding Idoc triggering
Idoc triggering
Regards,
Ahamed.

User exit not getting triggered while creating the vendor

Hi all,
I wanted to extend the idoc(crermas01) according to my reqiurement.
But when I am trying to create a vendor using the IDOC cremas01 the user exit EXIT_SAPLKD01_001 is not getting triggered.
Can anybody tell me the reason why it is happening so...........
Thanks and regards,
Vinil.

Is your Idoc generated after the execution?
Where is you break-point, it is inside EXIT_SAPLKD01_001. Please note FM EXIT_SAPLKD01_001 will not be called unless it is implemented using project (CMOD) and project is active.

Getting dump while loading master data

Hi,
i am gettin dump while loading master data genrated by copa,
that gtwa_not_assigned.
Best regards,
dushyant.

hi,
see weather that master data contain attribute or not,
if not than un check master data field from the master data attribute tab,
and than try to load it again.
Dushyant.

Not getting 'M' version of master Data

Hi SAP Gurus,
In SAP BI, I loaded Master Data (say vendor data) with Flat file and getting all the data in 'A' version & not in 'M' version.
What my assumption was: firstly the data should be in M version and then after activating Master data InfoObject, the data should go to Active version.
What i wanted is to have data in M version for all the data in new flat file irrespective of whetehr that data exists or not.
pls let me know
Thanks....

Hi there,
Thats the normal behaviour of the system.
The status 'M' only appears when modified data goes into your master data, otherwise it will always be in status 'A' active, that's why for new records you don't need to activate your master data, only to changed attributes.
Diogo.

Redefined method is not getting triggered while Debugging

Hi Experts,
I have a requirement wherein I need to desplay Role information in Header level. To achieve this I have enhanced component ICCMP_BP_DETAIL and Window ICCMP_BP_DETAIL/MoreWindow. I have redefined method IF_BSP_WD_HISTORY_STATE_DESCR~GET_STATE_DESCRIPTION of class ZL_ICCMP_BP_MOREWINDOW_IMPL. But, surprisingly, while debugging, flow is not coming to this redefined method, though it was coming in standard method. Please guide what can be the possible reason for this.
Regards,
Keya
Edited by: Keya Sit on Oct 14, 2009 2:32 PM

Hi Keya,
Hope you have activated your redefined method. Also check the configuration for controller replacement in SPRO and check the View Cluster-BSPWDVC_CMP_EXT.
Regards
Prasenjit

Enable User task is not getting triggered

Hi All
We have a provisioning workflow configured. "Enable User" task is not getting triggered while the user is enabled in OIM. Can anyone give a clue as to how to get it triggerd? Rest all the tasks are fine (Create, Disable, Delete, and other custom tasks)
Thanks,
Vinay

There is a OOTB scheduled Task "Enable After Start Date". once the user get enabled in OIM user profile. You have to run this task manually to have effect on corresponding RO for enablement. Else it will execute automatically as per scheduled time.
if the version of OIM is 11.1.1.5. There is an issue. update patch BP02. for same
--nayan

For the new delivery type created the Idoc is not getting triggered

Hi All,
I am facing the following problem:
For every outbound delivery getting created we have an Idoc which creates the file(sending the outbound delivery details), this file is sent to a system where the picking & packing of the goods happen. This process seems to be working fine for all the existing delivery types, but now we created a new delivery type for which the Idoc is not getting triggered.
Would like to understand what setting are we missing because of which the Idoc is not getting created for the new delivery type.
The Idoc being used is: DESADV01
Message type :DESADV
Thanks,
Geeta

I believe your existing idocs are created through a output type on the delivery ? if yes, probably you need to configure an existing output type / create a new output type for your new delivery type...

IDOC - Function Exit not getting triggered

I am doing an inbound IDOC for the message type WMMBXY and using basic type WMMBID02.
This is for goods movement based on PO.
I am doing an enhancement in the includeof the function module exit EXIT_SAPLLMDE_002.
This exit is supposed to get triggered for the message type WMMBXY.
when i tested the idoc in we19 it is sucessfully getting posted. I want to check my code in EXIT_SAPLLMDE_002. I have set breakpoint and tested using we19. But this is not getting triggered. But the idoc is getting sucessfully posted but with a status message 56 An inbound partner profile could not be found( I am not sure if this has something to do with above problem).

Did you attach your exit to a CMOD project and activated the same(CMOD transaction)?
The error you see regarding the partner profiles is probably due to the non existance of a partner profile for your idoc type in we20 transaction.
Maintain the inbound partner profile in we20 transacttion.

Urgent IDOC - EXIT_SAPLLMDE_002 not getting triggered.

I am doing an inbound idoc on message type WMMXY goods movement.
The idoc is sucessfully getting posted when tested through we19.
But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
I have activated the exit functional module, the project in CMOD is also activated.
Some one pls help me .. if u have its document pls post it to me.

Hi,
Please refer to this documentation of user-exit; may be of some help for you.
You can use this user exit to influence the processing of IDOCs of the
message type WMMBXY (goods movements) that are sent to SAP from external
systems via the MM-MOB or WM-LSR interfaces. You can also access
customer-specific processing in this case.
Call transaction and other important requirements
The user exit is performed in the function module that processes the
IDOCs of the message type WMMBXY, after the IDOC is withdrawn and
checked but before direct processing in the application has been
initiated. (That is, the data for the goods movement has already been
determined and edited, but the function module for updating this has not
yet been accessed. The standard function module for processing the
message type WMMBXY is called L_IDOC_INPUT_WMMBXY. The IDOC is processed
in an update task, which means that the source code is also executed in
the update.
If an error arises, then messages should not be issued since processing
is being carried out in the background and the result of processing must
always be returned to the ALE interface. For this reason language
elements such as MESSAGE, COMMIT WORK, LEAVE and the like should not be
used. If errors that should be passed on to the ALE interface or that
affect the result of processing are found in the user exit, you should
also use the user exit MWMIDI07(EXIT_SAPLLMDE_001) since it alone can be
used to take your errors into account (see documentation of the user
exit).
Parameters and options
The user exit in the program is the function module EXIT_SAPLLMDE_002.
In order to be able to use it, you must first create Include zxlidu10
and activate the enhancement by means of transaction CMOD. As
parameters, you can use the following data:
o   Goods movement data already determined from the received IDOC:
    -   Transaction code that is given along with the application
        function module (see interface description (import parameter
        X_TCODE).
    -   Indicator: post only if all items o.k. (import parameter X_XALLP
        ). This indicator must be set by default, to enable IDOC error
        processing.
    -   Indicator: Reset all tables (as primary call) (import parameter
        X_XALLR). This indicator is not set by default to enable the
        processing of several IDOCs. Normally you will not change these
        two indicators.
        -   Goods movement items table (table parameter T_IMSEG)
    o   Received IDOC data:
        -   IDOC control record (import parameter I_IDOC_CONTROL)
        -   IDOC data records (table parameter T_IDOC_DATA)
    This user exit can be used to:
    o   Influence the determined data for the goods movements. All data can
        be changed in this case.
    o   Analyze and process data that is transferred using customer-specific
        segments.
    o   Access additional activities.
    Examples
    A number of potential applications are described below.
A number of potential applications are described below.
o   You want to inform a user by mail when the goods movements of
     certain vendors or customers take place.
o   You want to start your own label printout, for example at goods
     receipt.
o   You want to update your own tables, for example statistical data.
o   You want to analyze a missing parts table at goods receipt and
     redirect the goods receipt correspondingly.
Reward points if helpful.
Regards,
Pankaj Sharma

IDOC - EXIT_SAPLLMDE_002 not getting triggered.

I am doing an inbound idoc on message type WMMXY goods movement.
The idoc is sucessfully getting posted when tested through we19.
But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
I have activated the exit functional module, the project in CMOD is also activated.
Some one pls help me .. if u have its document pls post it to me.

I am doing an inbound idoc on message type WMMXY goods movement.
The idoc is sucessfully getting posted when tested through we19.
But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
I have activated the exit functional module, the project in CMOD is also activated.
Some one pls help me .. if u have its document pls post it to me.

IDOC IDOC_OUTPUT_ORDERS not getting triggered

Im triggering an idoc IDOC_OUTPUT_ORDERS immediately when i create/change the PO
However the idoc is getting generated when i change only certain fields.
When i change other fields it does not get triggered.
Why?
-Dexter

Hi,
Check in the distribution model tcode BD64 if you have set some filter settings for the partner.
KR Jaideep,

Outbound Delivery Not getting created

Hi Gurus,
Outbound Delivery Not getting created
there is a DESADV IDOC that is supposed to create inbound dely, do the GR then create Outbound delivery and shipment (all automized). But this is not happening.
There is workflow set up that is blocking this...Task no TS95000019 is responsible for passing the values. This will show up in the SAP inbox with error description. But i am able to see TS95000018 but TS95000019 is not showing up in the workflow log.
Can anyone let me know what setting is missing in workflow so that this task shows up and i can make the system create outboud delivery and shipment automatically
Please help
Sunil

Sunil
First check whether that particular task is active in your client.
For a task to get triggerred you need to activate the triggerring settings.
Use PFTC T-code, input your task as TS and ID as 95000019
click on view button
Then click on " Triggerring Events" tab page.
View whether your task 95000019 is active. Green light will appear next to it in the left most column. If it is grey or red, then you need to change it to green. Only then it will work. Once this gets triggerred, subsequently it will pass the message to your inbox with correct error message and then only create an outbound delivery.
Hope this will help you out !
Regards,
Syed Nasir

Outbound IDOC not getting triggered while new master data is created

Similar Messages

Maybe you are looking for