Trigger condition for IDOC

Hi,
I have trigger condition for IDOC
All materials where:
"Finished Goods" Technical Names MARA-MTART = "Z001", and the Plants are "Granollers" MARC-WERKS="ES11", MARC-WERKS="ES12", goods that are "ready" or "ready for manufacturing", MARC-MMSTA = "02" or "03".
All the materials which satisfy this criteria will need to be triggered whenever a new material is created in SAP which meets the above criteria, or if any materials are modified which meet the above criteria in SAP.
How do I trigger my IDOC based on these conditions.
Regards,
Subhashini

Hi,
Please create the Idoc type / segments , create message type and link Idoc and message.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
2. Yes, you need LS & Partner profile
3. Yes use MASTER_IDOC_DISTRIBUTE
4. Can use IDOC_CREATE_ON_DATABASE instead of MASTER_IDOC_DISTRIBUTE and then process the Idoc.
Message Type :: The message type defines the semantic context of an IDoc. The message type tells the processing routines, how the message has to be interpreted. The same IDoc data can be sent with different message types.
IDoc Type :: An IDoc type defines the syntax of the IDoc data. It tells which segments are found in an Idoc and what fields the segments are made of.
Processing Code :: The processing code is a logical name that determines the processing routine. This points usually to a function module, but the processing routine can also be a workflow or an event.
The use of a logical processing code makes it easy to modify the processing routine for a series of partner profiles at once.
Partner profile :: Every sender-receiver relationship needs a profile defined. This one determines
The processing code
The processing times and conditions
In the case of outbound IDoc 1. The media port used to send the IDoc and 2. Triggers used to send the IDoc
Partner Type :: The IDoc partners are classified in logical groups. Such as : LS, KU, LI.
LS - Logical Systems : It is meant to be a different computer and was primarily introduced for use with the ALE functionality.
KU - Customer : The partner type customer is used in classical EDI transmission to designate a partner, that requires a service from your company or is in the role of a debtor with respect to your company, e.g. the payer, sold-to-party, ship-to-party.
LI - Supplier : The partner type supplier is used in classical EDI transmission to designate a partner, that delivers a service to your company.
thanks & Regards,
ShreeMohan

Similar Messages

Mandatory Fields for IDOC ORDERS01 for Pricing Condition EDI1 to trigger

Hi ,
I'm Testing an Inbound ORDRSP using we 19 for Pricing Conditions EDI1. What are the Mandatory Fields for IDOC ORDERS01
Thanks

hello,
I think it's better to execute VA01 to create a sales order; in that way you should have an idea of mandatory fields.
Thanks.

Configuring shipping point as Trigger point for posting outbound idoc

Hello All,
I have a requirement that on saving an Outbound Delivery(VL02N), an Outbound Idoc should be posted...but the condtion for posting the idoc should be its shipping point. I am not sure how to configure shipping point as the trigger point for the idoc.
Please suggest.
Thanks for your co-operation.
Regards
Anand

Hi Anand,
1. Go to transaction: NACE & select application V2 and click on output types.
2. change display <->Change mode.
3. select LAVA and press F6 (to copy Standard output type LAVA to ZLAV).
4. Give ur Z name for the new custom output type.
5. change access sequence from 0005 to 0012(shipping point).
6. Press ENTER and click copy all.
7. Now goto trasaction VV21, give the created output type name. ENTER
8. Maintain entries, shipping point, customer#, Medium as '6' ...etc
Now try VL01N with the given shipping point and check the output ZLAV has been triggered or not?
Let's see, if we miss any configs still!
Keep this as reference:
http://www.erpgenie.com/sapedi/messagecontrol.htm
Reddy

Filter conditions for Standard Idoc processing

Hi Experts,
       In BD64 - Distribution model , I have created filters for MATMAS based on Division, Sales Organization, Distribution channel and Material Type.
when I process the IDoc through BD10 - Send material it is not getting filtered based on the conditions set in BD64.
eg) I have created a material in a particular sales organization for which the data should not be processed through Idoc based on the filter condition set for sales org in BD64.
   But now that the condition is not been checked and the Idoc is processed when i send it through BD10.
whether BD10 will not check for the filter conditions?

hi asik,
partner in the generated idoc and in BD64 as a Receiver are the same.
I am using single filter group in BD64 ( Matmas ) for Division , Sales Org, Distribution channel and material type.
The filter group comprises the following filters:
Division                             - 01
Division                             - 02
Sale org                            - ABCD
Sale org                            - EFGH
Distribution channel          - AA
Distribution channel          - BB
Mtrl Type                          - SPAR
Mtrl Type                          - FNGD
These result in the filter conditions should be like
(Division 01 OR division 02)
and
(sale org ABCD or EFGH)
and
(Dst Channel AA or BB)
and
(mtrl type    SPAR or FNGD )
Scenario for idoc processing
                                         Division          01
                                         sale org         xxxx
                                         dst channel   AA
                                         mtrl type        FNGD
the Idoc should not be processed for the above scenario
but its triggering an Idoc when I test it through BD10.

Trigger Output Condition for EDI Medium

I need to trigger output for one Z Order Type which is having the medium as EDI.
I am aware of FM WFMC_MESSAGE_SINGLE which could trigger output for print medium (Doesn't work EDI medium 6) .
I need a similar FM but for EDI.
Thanks
Anand

Hi
Check the following fun Modules
WFMC_MESSAGES_SELECT_PA
WFMC_MESSAGES_EXTEND
WFMC_MESSAGES_PROCESS
WFMC_MESSAGES_SELECT
WFMC_MESSAGES_SELECT_ALL_FALSE
WFMC_MESSAGE_SINGLE_NO_UPDATE
WFMC_MESSAGE_SINGLE_SCREEN
Reward points for useful Answers
Regards
Anji

How to set the conditions for item deletion approval workflow?

Hi,
I have created approval workflow for item modifications ie, when user try to modify an item, it will send a mail to Project Manager. For that I set the conditions in Change the behavior of the overall task: 1. When the task process starts 2 . When the task
process completes .
Change the behavior of the single task: 1.when a task is Pending.
[I followed this https://www.nothingbutsharepoint.com/sites/eusp/Pages/5-Steps-to-Enhance-SharePoint-2010-Approval-Workflow.aspx ]
My Requirement is that I want to set this same workflow for the scenario: when the user deletes an item it will send a mail (intimation mail for item deletion) to Project Manager. here i dont want to send modification mails when user deletes an item.
When user modifies an item: 1. intimation mail, 2. Approve/Reject mail 3. intimation for approval / rejection mail.
When user deletes an item: 1. intimation mail.
How can we set it in one approval workflow?? where i have to set the condition for sending either item modification mails or deletion mail.
Thanks,
Praveen ji

Hi,
According to your post, my understanding is that you wanted to start approval workflow when item deleted.
You should first make some changes to trigger the workflow when you delete the item.
You can use the Event Receiver to achieve it.
In order to trigger workflow on item delete you need to create event receivers and from event receiver call the workflow already attached with list.
http://ravendra.wordpress.com/sharepoint-workflow-on-list-item-delete/
You can also create custom action to start the workflow, you can refer to the following article, then modify the workflow as your need.
http://blogs.sharepoint911.com/blogs/jennifer/Lists/Posts/Post.aspx?ID=50
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Creating a correct trigger condition

hi All,
I have a problem in my trigger condition in my query.
The background:
1. I have a List view with a Data insertion (Lead Select) into a ROW.
2. Also, I have 5 different queries which are triggered based on a selection of a Radio button.
Now, my req is that Query1 should load either on
                                                         change of Lead select in List View
                                                   OR if the chosen Radio button is 1
Query2 should load either on
                                                         change of Lead select in List View
                                                   OR if the chosen Radio button is 2
& so on.
Can you please help me with a valid trigger condition. ? The concatenate is not working as the Xcel only allows Value Change or Value Becomes.
Currently, I am launching all the 6 queries at once using CONCATENATE + VALUE CHANGE. This is a huge hit on performance.
Cheers
Kiran

What if you have 5 different cells (one for each query) and you only have the trigger cell for Query 1 show the list select value only if the chosen radio button is 1 and so on?
Formula for Query 1 Trigger Cell: =If(=1,,"")
Formula for Query 2 Trigger Cell: =If(=2,,"")
~~~~~~~~~~~~~~~
Formula for Query 5 Trigger Cell: =If(=5,,"")
Then, the value in any given cell should update any time the radio button is changed (from "" to the ListSelectValue) and anytime the ListSelect value changes (assuming that radio button is selected).

Activating conditions for Purchase Order workflows in EBP

Dear SRMer's,
I am facing the following problem:
System Info :SRM Server 5.5, ECC 6.0
Scenario 1:
All start conditions for Purchase Order in SAP Business Workflow are activated.
I created a direct procurement shopping cart (DP) in SRM browser and ordered it, then I logged in as proffessional purchaser, changed the Price and processed the DP PO.
When Ordering, the follow on Documents are created, but says the PO is waiting for approval. When I check for this PO in the Backend R/3 system in the Me22n (Display PO changes), I don't see the PO.
Scenario 2:
All Start conditions for Purchase Order in SAP Business Workflow are de-activated
I created another direct procurement shopping cart (DP2) in SRM browser and ordered it, then I logged in as proffessional purchaser, changed the Price and processed the DP2 PO (Status is held).
When Ordering, I get the Warning message, no workflow found, contact system administrator.
Please advice what needs to be configured for the PO to be ordered successfully.
Thanks in advance
Raj

Hi,
In your scenario 1, if system is saying that there the PO has to be approved, it means that you have managed the user that will receive the workitem..
Activating all PO WF is not a solution as in standard there are two many cases activated (amount, role, limit...)
I propose you to first activate only the 0 step WF and to overwrite the code inside
Just code that every PO modification should trigger O step WF thus it will be more simple to test it.
Later on, if you want to implement more complex starting conditions, you just have to modify the WF content...
Kind regards,
Yann

Route of the operator.... while creating mapping for idoc to file

Hi,
Scenario is IDOC to File but certain rules are there while creating a mapping in XI.
This is the description for my scenario :
Within XI this Idoc message needs to be translated into 2 text files:
1 file for the route of the operator
     - Read the idoc data.
     - When reading a new order first get the customer. This will be a new line in the file.
        The customer number will be set into the filed u2018CustomerIDu2019.
     - Then read the items. For every item create a new line in the file. The machine number will be mapped to the field CustomerID
     - The field RouteOrder should get a sequential number. Starting at 001 and updated by 1 for every new line.
Could you please guide me how can i implement this above scenario.
Regards,
Y.Raj

Within XI this Idoc message needs to be translated into 2 text files:
this can be done using multimapping i.e. defining your target messages at mapping tabs in your message mapping.
When reading a new order first get the customer. This will be a new line in the file.
The customer number will be set into the filed u2018CustomerIDu2019.
If there is some condition for identifying new order then you should put condition based on input field.
if customer no doesnot exists in order then RFC lookup can fetch customerno
The field RouteOrder should get a sequential number. Starting at 001 and updated by 1 for every new line.
for this declare varaible in global section and use the same or some builtin function can be used for the same.
Rajesh

Pricing condition in idoc PORDCR05

Hi all,
Our current business process is- we will get POs from our legacy system in flat files, SAP will convert these into idoc basic type PORDCR05 / message type PORDCR. We are using BAPI_PO_CREATE to create PO from idoc.
New requirement is to send pricing conditions (freight fees) from legacy in the same flat file and insert them into SAP PO using condition types.
We can configure new freight condition types, but my question is can we populate pricing conditions in idoc basic type PORDCR05 / message type PORDCR? Do we have standard segment for this or do we need to go with idoc extension?
Also can BAPI_PO_CREATE handle pricing conditions?
Thanks,
Pat.

You should use BAPI_PO_CREATE1 instead of this old BAPI and read OSS note 580225 - Purchasing BAPIs: Conditions and pricing

Enhanced Interface Determination for IDOCs

Hi All,
I've a query on the usage of Enhanced Interface Determination for IDocs.
I've to create IDocs based on the condition in the Message Mapping i.e. say if recordtype in the source is A then IDoc1 should be created and if recordtype is B then IDoc2 should be created.
Is it possible to use Enhanced Interface Determination to achieve this??.. Because I was told by someone that Enhanced Interface Determination can't be used for IDoc based scenarios though am using External Definitions for the mapping purpose. Please clarify.
Thanks in advance
Regards,
Joe.

Hi Sridhar/ Bhavesh,
Thanks for your prompt reply. I think I wasn't clear in my previous post.
The scenario is the input file has three different record types (3 different structures) and the IDocs should be created based on the record type. I don't think I can use the condition based scenario as the record types are totally different. Please suggest.
Thanks,
Joe.

Pls send material for idocs in ECC 6.0

Pls send material for idocs in ECC6.0

Hi sitaram s ,
IDoc
- IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Archiving Processed IDocs
IDoc archiving is a two-step process:
1. Archive the IDoc.
2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
Transaction SARA works in the following way:
On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
SAP Integration Using ALE(Application Linking and Enabling)
- IDOCS -
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
ALE Inbound Pre-Processing
http://www.erpgenie.com/sapedi/idoc_abap.htm
cheers!
gyanaraj
reward points if u find this helpful

Starting Conditions for Purchase Order WF

Hi all,
We have developed a Workflow (Process-Controlled Workflow) for SRM Purchase Order. The requirement we have is that if the PO is released and then changed, only the WF should start again if the amount is changed. Any other field change in the PO should not trigger WF again.
There is customizing to define which fields should trigger WF for Shopping Cart, but I don´t found this for Purchase Order:
PRO--> SRM server --> sourcing--> Define Fields in Shopping Cart Which Trigger Workflow
Any suggestions?
Many thanks,
Ezequiel

Hi,
In your scenario 1, if system is saying that there the PO has to be approved, it means that you have managed the user that will receive the workitem..
Activating all PO WF is not a solution as in standard there are two many cases activated (amount, role, limit...)
I propose you to first activate only the 0 step WF and to overwrite the code inside
Just code that every PO modification should trigger O step WF thus it will be more simple to test it.
Later on, if you want to implement more complex starting conditions, you just have to modify the WF content...
Kind regards,
Yann

In 10.2 docucorp, how to add a manual condition for a group

Hi,
I've grouped some faps in 10.2 by applying groupbegin and group end rules. Can I add a common manual condition for this group in 10.2?
Thanks,
Sai krishna

Hi Sai krishna,
No, sorry can't do it. The ability to add a "common" trigger to a group of faps appeared in release 11.3, when the concept of sub-forms was first introduced.
Gaétan

Process code for IDOC Output from MIRO

Hi,
We need to find the Process code for IDOC output to assign Output type in ECC. We need the IDOC output to some other system like PR while doing the invoice Posting (Transaction code MIRO). We tried Using process code SD09 for the IDOC with IDOC Type INVOIC02. In SD09 we are getting error (Update terminated) when we trigger the output while saving in MIRO transaction.
Further we understand that process code SD09 is used for SD billing and Invoice process.
We need your help in
1. getting the correct process code for the IDOC generation for Invoice posting thru MIRO.
2. If we need to configure one process code, let me know the correct function module for the same.
Please Note, we need this as Output Idoc from Invoice Posting MM (MIRO).

Hi Shankar,
Thanks for quick for reply. We have tested this process code with IDoc type - GSVERF03 and message type - GSVERF. It worked for us for MIRO transaction.
we are testing with IDoc type INVOIC02.
once again thanks for sharing the process code.
Regards,
Brahma

Trigger condition for IDOC

Similar Messages

Maybe you are looking for