Identify New or Change for BOMMAT IDOC in SAP

Hi Experts,
We need help in identifying if particular BOM is new (i.e. CREATE) or CHANGE using IDOC data.
But we see IDOC_MSGFN values is not consistent, it is always "005", so we are not able to identify whether it is create or change.
Is there any other way we can identify using IDOC values if its new or change?
Regards,
Sanjana

USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Transaction Code - MM41                     Create Material &
Exit Name           Description
MGW00001            Material Master (Retail): Additional Data
MGW00002            Material Master (Retail): Number Assignment
No of Exits:          2
Transaction Code - MM42                     Change Material &
Exit Name           Description
MGW00001            Material Master (Retail): Additional Data
MGW00002            Material Master (Retail): Number Assignment
No of Exits:          2
Rewards if useful.........
Minal

Similar Messages

Can we create new partner types for quallity notifications in SAP system?

Can we create new partner types for quallity notifications in SAP system?
The business requirement is to limit the available entries for partners displayed when they search in quality notification. I have already created new partner functions & assigned the relevant partner types, however struggling with defining new partner types.
Would appreciate help in resolving this.
Thanks,
Nilesh

I know this customisation setting ...It allows us to create the partner functions & assign it to the partner determination procedure.
Then you can assign the procedure to the notification type.
This customisation setting does not solve the problem I have.
I'm looking for the partner type creation process which we assign to the partner function.
Edited by: NILESH BHAVE on Aug 12, 2010 3:06 PM

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

Trying to identify what to change for user who has permissions on a library but gets no search results from the library

We are running SP 2010 service pack 2.
Search is working for people in general.
Yesterday user Y asked me why they (user Y) does not get results when they search for documents in the library. They get results back when searching other libraries.
The library has a limited number of users who can access.
The user is explicitly added to the library's permissions with Read permission.
When I look inside the library at specific documents, the user is listed as having Contribute,Limited Access privs on each document.
As an admin, I have accessed the site and performed searches and gotten results. Others on the site with various permissions get results back.
So it appears that search is working.
What other things can I check - via powershell perhaps - to help identify and resolve user Y's dilemma?

What we found is this.
At the site level, only 4 users have access. At the library level, 3 more users were added directly and given read permission.
These three users could see the contents of the library, read the documents of the library, but when they attempted to search the library, got "Access Denied".
I was able to negotiate for a resolution of this problem for us to create a new SharePoint group for the site, give it Read permissions,
and add that group to the library permissions. I informed the owner that he could check other libraries and lists and remove that group if there were things there that should not be accesible.
I also warned him that if he were to put something confidential in, say, the announcements section, he would need to remove the group from that list as well if he didn't want the people to see that.
So, the users now can see the results page, which is returned as a URL immediately under the site.
There were a couple other work arounds that we could have tried - moving the shared library to its own subsite with different permissions than the parent site, or having the users use the enterprise search and to refine the results down to the specific library.
Thank you for your question!.

EOIO should be enabled for Inbound IDocs to SAP

Hi All,
My Interface requirement:
i want to send my IDoC's to SAP ECC from SAP PI using IDoc Adapter in EOIO manner. so i have followed the below link.
http://help.sap.com/saphelp_nwpi71/helpdata/EN/96/791c42375d5033e10000000a155106/frameset.htm
1)I have have enabled EOIO in sender File adapter.
2)i have checked the Queue Processing in IDoC adapter.
assumed that IDocs are processing in EOIO manner. for proving the same, i have stopped the RFCUSER which is in ECC to process the IDOCs to SAP.
but still messages are stuck in Trfc queue, so i am thinking that EOIO is not enabled as messages are not stuck in SMQ1.
how to achive EOIO for inbound IDoCS??
Thank You,
Madhav

Hi
It's fine that messages are not stuck in smq2 on PI side. You set in smq1 system, connection and assing connetion pool numer and meesage is transfered to Ecc using common connection. On target Ecc check tcode WEINBQUEUE.
Br
Maciej

QRFC/TRFC for sending idocs from SAP system to XI

Hi experts,
The standard program RFFOEDI1 generates payment orders - first PEXR2002 and then EUPEXR idocs. These idocs are to be sent to the bank from SAP through XI. Bank partner profile is maintained. But these idocs because of TRFC are not getting sent in the order in which they are generated by the SAP system. So I changed the bank partner profile settings from TRFC to QRFC and gave the rule name as first 16 of mes type. But the idocs are struck in the SAP system. Is there any standard program to be run to send the idocs out from SAP system or is it automatic.
Please suggest a standard method which is to be followed to send the idocs in the same order in which they are getting generated for the scenairo above.
Regards,
Asha

Hi Asha,
As you said Idocs are stucking,
To send Idocs to XI, you must have maintain some settings in XI to receive Idocs. Once they are done properly .in R3 side standard way to send idocs to XI is Maintaining Change Pointers and shedule the programe to trigger that most of Standard idocs will have standard programs to catch change pointers and send them to external system.
and to maintain the same order of idocs there is a setting called Quality Of Service in XI side ,that option should be set to Exactly Once In Order .
Regards,
Ramesh.

Send Changes for IDOC ORDRSP

Hi Gurus
Can anyone help me in sending the changes for the IDOC for transactional data.
For Sales Order IDOC -- ORDRSP.
When newly sales order is created, all the sales order information should be sent. --This is not a problem.
When changes are done on the sales order -- Only the changes should be sent in the IDOC. I have activated the change pointers in BD50, BD51 for ORDRSP and in BD52 created the entries for ORDRSP.
but when i trigger the IDOC using the output type, i get to see all the data instead of only the changes.
Is there anything that i am missing???
Any help is really appreciated.
Thanks
Saritha

Hi Linda,
I have documentataion on ALE/IDOCs which may not be helpful to you. If u need that i can send u .
Instead i can help u out if u r facing any issue.
In our case: wen ever sales order is created /changed an idoc shud be genrated.
This can be done thru Message control.
Which involves customization from functional guys in NACE as well as Technical guy in Partner profile/port..
do let me know where ever u r not clear.
regards,
Naveen

Which all configurations you need to do in R/3 for an Idoc to file scenario

which all configurations you need to do in R/3 for an Idoc to file scenario?
Rgds
Ruchitha

Hi ruchitha thakur ,
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
Integration Builder
Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1
The following web-sites give u step-by-step solution to configure R/3 :
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Step by Step Procedure of IDOC to File Scenario using BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
cheers!
gyanaraj
****Pls reward points if u find this useful

ALE configuration for Outbound Idoc - Help me

Hi Experts,
I am newbee in SAP and XI. I was trying to send MATMAS Idoc from R3 and i was running into some issues. So i would appreciate if someone can help me.
I am using following link as reference. /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I did all the steps mentioned in the above link ( Creating Logical Systems, Assigning Client and RFC destnations, Creating distribution models ..... etc)
and then everything went well and i saw success messags in all the steps.
I used BD10 to send material and it went well. But when i check TRFC queue, i see some error messages; "No service for system SAPRDI, client 800 in Integrion Directory"
And all the messages are hanging in the TRFC queue.
Note: I havent configured anything in XI yet. I wanted to make sure IDoc gets to XI client first.
Thank you in advance. Pls help me its very urgent.
Thanks,
Surya

I created RFC destination (SM59) and Port (IDX1)
Then i sent another material (BD10) and checked tRFC queue. i found bunch of error in the Queue.
1.connection to host 10.4.23.120, service sapgw00 timed out / CPI-C error C
No service for system SAPRDI, client 800 in Integration Directory
partner not reached (host 10.16.176.29, service sapgw00) / CPI-C error CM
connection to host 10.16.136.127, service sapgw58 timed out / CPI-C error
Note: i have noticed entries for R3 in SLD as below
System Name: RDI ( not SAPRDI as mentioned in the error message)
System Home: r3ides
That might be reason. If so, how to change it in R3 box? Any suggestions?
Please send me if you guys have any links or docs to address this issue.
Thanks,
Surya

Send Idoc to SAP in sequence and roll back if the last one fails

Hi All
I have a scenario like this.
System Ajore --> XI - > R/3
Ajore is a manufacturing system
Send material from Ajore to SAP through XI and create MATMAS idoc in SAP
Send change number from the Ajore to SAP through XI and create ECMMAS idoc in SAP
Send Bill of materials from the Ajore to SAP through XI and create BOMMAT idoc in SAP
All these will should be send in the sequence MATMAS, ECMMAS, BOMMAT to SAP. How can I achieve the sequence operation through XI?
Second challenge is when I send the BOMMAT to SAP and if it fails, then all the processed MATMAS, ECMMAS sent to SAP should be rolled back.
Is it possible to achieve using XI?
The reqmt is very urgent. Any help is really appreciated.
Thanks
Ricky

Hi Satish,
Thanks for the reply. Do I need to do event driven message processsing in XI for this? The other way is to schedule the RBDAPP01 in R/3 to post idocs in sequence based on the message type and Partner number
Does this makes sense?
And any idea bout the second question for roll back?
Thanks

Error while pushing idocs from SAP to XI

Dear All,
For doing ALE configurations for pushing IDOC's from SAP to XI, I am following the following blog posted on SDN:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I am able to create the model view distribution successfully but when I am clicking on EDIT --> MODEL VIEW --> DISTRIBUTE (which is one of the steps mentioned in the blog), I am getting an error tht
Target system XIDEV Communication error occurred
User is locked. Please notify the person responsible
please tell me what is the error ie which user is locked and how should i proceed now.
Waiting for your reply.
Warm regards,
N.Jain

hi krishnamoorthy,
i hve created one RFC in my R/3 system which is pointing to Xi-DEV. So, in the RFC I have used my XI user id & password for loging and the RFC is wrking fine when I am testing tht. I have used my id "XISUPER" in that RFC and it is not locked in XI-DEV. I have not used user id "XI_APPLUSER" anywhere.
Please suggest.
Warm Regards,
N.Jain

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
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 for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

ALE: mapping IDoc fields to change document fields - TBD22 for ADRMAS iDoc

Hi,
I am currently try to find a table or way to extract the information of the TBD22 table (ALE: mapping IDoc fields to change document fields) for the iDocs/ Message Types:
ADRMAS
INTERNAL_ORDER
PROJECT
I am looking for a table that shows me to which SAP R/3 tables and fields the segments and fields of the above mentioned messages will be mapped to.
When I add one of the above mentioned message types to the table TBD22 selection criteria I always receive the notification: "No table entries found for specific key".
Could anybody determine Which table I have to use or why I cannot extract this information?
Thanks in advance!
Best regards

Hi,
Since we can not map the target IDOC when any of the field changes using nodefunctions , you can write UDF and check the same i.e if field1 changes or field2 changes or field3 changes then trigger new IDoc. This is one of the options that you can try...please try it once.
Regards
Priyanka

BOMMAT Idoc for Phantom assembly

I have to send BOM to SAP-ME using BOMMAT Idoc. I would like to know how the Idoc behaves for Phantom assembly.
For header material A, I have 2 components say B & C. C is a phantom (MRP2-Spl Proc Key=50). And C has a BOM with components D & E.
Now I want to generate Idoc for BOM for A. Will the item level segment in Idoc for A will have B &C only or B, D and E. i .e will it skip Phantom component?
Regards
Shiju

Hi,
Your requirement is not very clear.
Assuming that you want to create an Idoc say for BOM(phantom assembly), the following are the steps:
1. Goto WE02 (list of Idocs)
2. Give FINSTA in Logical Message field then, execute.
3. Take the reference of any Idoc with status 53 (Green).
4. Goto WE19 (to create new Idoc with reference)
5. Give the Existing Idoc no. as selected in Point 3, execute.
6. Give all the parameters as per your new House Bank.
7. Click Standard Inbound button and note the Idoc No.
8. Goto WE02, give the Idoc No. as per Point 7, execute
9. The status has to be 53, else look for the error log.
10. Goto BD87 to make corrections in Idoc and execute.
The above steps are at a high level to kick start the creation of Idocs.
Cheers
Chandra

I created a new Apple ID for iCloud on my iPhone, but I can't seem to find a way to "sign out" or "log out" of that Apple ID (for iCloud) to sign in with another Apple ID. The only account login I could change was the Store. How do I "log out"

I created a new Apple ID for iCloud on my iPhone, but I can't seem to find a way to "sign out" or "log out" of that Apple ID (for iCloud) to sign in with another Apple ID. The only account login I could change was the Store.
How do I "log out" or "sign out" of iCloud on my iPhone? There is an option to delete the account, but I just want to log off. I want to keep the account name for future use.

@fernandamagalhaes
It looks like the article below has the information you are looking for.
iCloud: Change iCloud feature settings
http://support.apple.com/kb/PH2613
Turn off iCloud completely
Depending on whether you want to stop using iCloud on all or only some devices, do one or more of the following:
On your iOS device’s Home screen, go to Settings > iCloud, then at the bottom of the screen, tap Delete Account.
Note: If you delete your iCloud account, iCloud will no longer back up your iOS data. You can still back up your device in iTunes (for more information, open iTunes and choose iTunes > Help).
On your Mac, open iCloud preferences, then click Sign Out.
If your Mac has OS X v10.7.5 and you turn off iCloud, your calendar information and reminders aren’t stored locally in iCal. If you want to retain your calendar and reminder information, you need to back it up before turning off iCloud. For more information, see the Apple Support article iCloud: Calendar & reminder data removed from Calendar and Reminders or iCal when disabling iCloud Calendar.
On your Windows computer, open the iCloud Control Panel, then click Sign Out.
Note: If you turned on automatic download of music, app, or book purchases (in iTunes preferences or in Settings on your iOS device), your iTunes purchases are still downloaded to your devices.
Set up iCloud on your devices

Identify New or Change for BOMMAT IDOC in SAP

Similar Messages

Maybe you are looking for