Difference between IDOC for creation, change and deletion

Hi,
As per the requirement, an IDOC will be generated for PO, Vendor Masters and Goods receipt when ever a PO or Vendor or Goods receipt is created or changed. How can we identify whether the IDOC has been created for creation or change of a particular thing? Is there any identifier where in we can check whether the IDOC generated is for creation or change?
And also how to identify that a particular PO or VM or GR has been deleted or cancelled?
Thanks & Best Regards,
Phani.

hi,
to check the idoc status ie idoc created or changed --use transaction WE05
we02 to diplay idoc
please rewrd points if helpful,
shylaja

Similar Messages

Create ORDRSP Idoc on creation, change or deletion of outbound delivery

We have ORDRSP Idocs being created when a sales order is created or modified. Now our customer would like an ORDRSP Idoc sent to them when the outbound delivery is created for the sales order. The reason that the customer would like an additional ORDRSP sent is because the time between the entry of the sales order and the creation of the outbound delivery may be a few weeks or more and the actual delivery may not be able to satisfy the quantity ordered. The customer is not set up to allow partial deliveries.
The customer uses the ORDRSP to feed into their billing system and would like updated quantities at delivery time. They do not want an ASN record.
Does anyone have any ideas or suggestions on how to trigger the ORDRSP Idoc when the delivery is created, modified or deleted? We are on SAP release ECC 6.0
Thanks for any help,
Russell

Vinit and Abhishek,
Thanks for your replies and information. Sorry I was not clear in my question. The ORDRSP Idoc is already being created when the order is created or changed. ORDRSP works fine. The partner profile is set up, NACE is already configured for ORDRSP, change pointer is working properly, output determination is configured and working, the ORDRSP Idoc is being created.
What I would additionally like to do is trigger the creation of an ORDRSP Idoc when the delivery for the order is created or modified. I suspect this will require using a user exit in the delivery program to trigger the ORDRSP Idoc and not standard SAP configuration. This is what I would like help on (trigger the creation of an ORDRSP Idoc when the delivery for the order is created or modified).
Also this site is a small shop. I am the ABAP programmer, the functional consultant and the EDI consultant for all SAP modules. There is no one else on the team here other than one person that does transports and security for SAP.
Thanks,
Russell

Event for Material Change and Delete

Experts,
Is any Standard events available to trigger the workflow when the material is changed or deleted from the material master.

First check any event is getting Triggered or not. If yes job done use it if not then find user Exit from which you can trigger event by writing code.
You can make use of FM
SAP_WAPI_CREATE_EVENT
SWE_EVENT_CREATE
to trigger custom event.
You can check this code
FUNCTION zwf_process_honorarium .
""Local Interface:
*" IMPORTING
*"     VALUE(I_EMP_NUMBER) TYPE PERNR_D
*"     VALUE(I_EMP_NAME) TYPE ENAME
*"     VALUE(I_BEGIN_DATE) TYPE BEGDA
*"     VALUE(I_CURRENT_SAL) TYPE ANSAL
*"     VALUE(I_HON_SAL_GRD) TYPE TRFGR
*"     VALUE(I_HONORARIUM_SAL) TYPE ANSAL
*"     VALUE(I_JUSTIFICATION) TYPE CHAR100
*"     VALUE(I_PERCENT_DUTY) TYPE INT1
*"     VALUE(I_END_DATE) TYPE ENDDA
INCLUDE <cntn01> .
DATA:i_emp_details TYPE STANDARD TABLE OF p0001, "Employee Details
       wa_request    TYPE p0001,                    "Workarea for Employee details
       v_country_grp TYPE molga,                    "Country SubGrouping
       v_object_key TYPE sweinstcou-objkey,        "Key for the buisness object ZWOBUSHONO
       v_request_det TYPE zwf_ms_honorarium.        "PCR data
CONSTANTS: c_bo_hono     TYPE swo_objtyp VALUE 'ZWOBUSHONO',
             c_event_hono TYPE swo_event VALUE 'HonReq',
             c_infy_type_1 TYPE infty      VALUE '0001'.
Event Container declaration
swc_container i_event_cont.
swc_create_container i_event_cont.
Reading the INFO TYPE 0001 to obtain the
Employee details
CALL FUNCTION 'HR_READ_INFOTYPE'
    EXPORTING
      pernr           = i_emp_number
      infty           = c_infy_type_1
      begda           = sy-datum
      endda           = sy-datum
    TABLES
      infty_tab       = i_emp_details
    EXCEPTIONS
      infty_not_found = 1
      OTHERS          = 2.
SY-SUBRC check is not required as the error
handelling will be done by WorkFlow rule
resolution.
Filling up the PCR data in structure v_request_det
which will be passed to event container.
v_request_det-emp_number     = i_emp_number.
v_request_det-name           = i_emp_name.
v_request_det-begin_date     = i_begin_date.
v_request_det-current_sal    = i_current_sal.
v_request_det-hon_grade      = i_hon_sal_grd.
v_request_det-hon_grd_sal    = i_honorarium_sal.
v_request_det-justification = i_justification.
v_request_det-percent_duty   = i_percent_duty.
v_request_det-end_date       = i_end_date.
CLEAR wa_request.
READ TABLE i_emp_details INTO wa_request INDEX 1.
IF sy-subrc = 0.
Retrieving the Country SubGrouping for the employee
    SELECT SINGLE molga
      FROM t001p
      INTO v_country_grp
     WHERE werks = wa_request-werks
       AND btrtl = wa_request-persk.
ENDIF.
Sending the relevant data to event container
swc_set_element i_event_cont 'RequestData'     v_request_det.
IF sy-subrc <> 0.
No Processing needed.
ENDIF.
swc_set_element i_event_cont 'PersonalArea'    wa_request-werks.
IF sy-subrc <> 0.
No Processing needed.
ENDIF.
swc_set_element i_event_cont 'CountryGrouping' v_country_grp.
IF sy-subrc <> 0.
No Processing needed.
ENDIF.
swc_set_element i_event_cont 'EmpSubGrp'       wa_request-persk.
IF sy-subrc <> 0.
No Processing needed.
ENDIF.
Raising the event to trigger the workflow
v_object_key = i_emp_number.
CALL FUNCTION 'SWE_EVENT_CREATE'
    EXPORTING
      objtype           = c_bo_hono
      objkey            = v_object_key
      event             = c_event_hono
    TABLES
      event_container   = i_event_cont
    EXCEPTIONS
      objtype_not_found = 1
      OTHERS            = 2.
IF sy-subrc <> 0.
No Processing needed.
ENDIF.
COMMIT WORK.
Thanks
Arghadip

Differences between Automatic Receipts Creation Program and Master Program

This is something I observed today - I'm hoping someone can explain it to me.
If I go through the Receipt Batches form and create a new batch for Automatic Receipts, this calls the Automatic Receipts Creation Program and my batch gets created successfully.
If I launch the concurrent request Automatic Receipts Master Program, no receipts are created. But there are invoices in the system eligible for receipting.
I'm trying to understand what the Automatic Receipts Master Program does differently? What does it do in general?

This is something I observed today - I'm hoping someone can explain it to me.
If I go through the Receipt Batches form and create a new batch for Automatic Receipts, this calls the Automatic Receipts Creation Program and my batch gets created successfully.
If I launch the concurrent request Automatic Receipts Master Program, no receipts are created. But there are invoices in the system eligible for receipting.
I'm trying to understand what the Automatic Receipts Master Program does differently? What does it do in general?

Difference between " COMPRESS FOR ALL OPERATIONS" and "COMPRESS FOR OLTP"?

I was looking through Oracle's OLTP Table Compression (11g onwards) documentation as well as online resources to find the syntax and came across two different versions:
COMPRESS FOR ALL OPERATIONS
and
COMPRESS FOR OLTP
The documentation I looked through didn't mention any alternative syntax, so i was wondering if anyone here might know the difference.
Thank you!

Table Compression Enhancements in Oracle Database 11G Rel1 as as follows:
The compression clause can be specified at the tablespace, table or partition level with the following options:
•NOCOMPRESS - The table or partition is not compressed. This is the default action when no compression clause is specified.
•COMPRESS - This option is considered suitable for data warehouse systems. Compression is enabled on the table or partition during direct-path inserts only.
•COMPRESS FOR DIRECT_LOAD OPERATIONS - This option has the same affect as the simple COMPRESS keyword.
•COMPRESS FOR ALL OPERATIONS - This option is considered suitable for OLTP systems. As the name implies, this option enables compression for all operations, including regular DML statements. This option requires the COMPATIBLE initialization parameter to be set to 11.1.0 or higher.

Difference between SKFs for Cost Centers and Profit Centers

Dear All,
Three cost centers A,B and C have two profit centers say X and Y assigned. When we run SKFs report for Cost Centers - S_ALR_87013645 total for all the Cost centers is say 30 (81210). When I run the report S_ALR_87013342 for Profit Centers SKF break down total is 30. However break up is not matching. Cost Center A and B have Profit Center X and C has Profit Center Y. Ideally in PCs break down for SKFs must be X = 20 and Y=10. However this is not the case. Total is tallying but the break up is not tallying. Y has total of say 25.
Cost Center C has profit center assignment changed in the middle of the year. Is the difference because of changing the PC assignment to CC in the middle of the year/in between? Do we need to adjust the SKF numbers for incorrect PCs in 9KE5?
Is there any other way to correct the difference instead of posting in 9KE5? Please help.
Thanks in advance,
Satya

found it

Distinguishing between IDocs for Delivery, Shipment and Invoice

Hi Experts,
I have a requirement where I am triggering IDocs from SAP for Delivery Document, Shipment and Invoice and sending them to a third-party middleware everytime they are created in SAP, by configuring output types for these documents.
I want to know if we have any field in these IDocs's Structures that can be used to distinguish between the different documents such that we can identify which document has been received based on this field (or combination of fields)?
I tried to use Document Category for this purpose, but this field is not available in Invoice and moreover, the IDoc Segment names are different for every IDoc's message type.
The key point here is that I am not allowed to do any sort of Customization in SAP to achieve this and I can only go about using the Standard Functions inherently available in SAP.
Please suggest a possible solution for this predicament of mine.
Thanks in advance.
Regards,
Keerthi

Hello Keerthi
I do not see where the problem lies.
We exchange via FTP share similar documents with one of our logistics partner:
Inbound delivery (VL33N) => sent as DESADV.DELVRY03 => converted on SAP-XI to TRADACOMS ORDHDR => file suffix .LTI
Shipping Order (VL03N) => sent as SHPORD.DELVRY03 => converted on SAP-XI to TRADACOMS ORDHDR => file suffix .LTO
I am not a fan of functional file names yet if the third-party tools is not capable to distinguish between the documents based on their contents at runtime then we need old-fashioned unique file suffixes.
Of course the two ORDHDR messages can be distinguished based on their contents. The message contains a TYP segment with the following qualifiers:
TYP/TYP2 = '0430' = (shipping) order (= outbound delivery)
TYP/TYP2 = '0660' = inbound delivery
From this logistics partner we receive two different kinds of DLCHDR (delivery confirmation) messages:
TYP/TYP2 = '0670' = Proof of Delivery for (shipping) order => mapped to STPPOD.DELVRY03
TYP/TYP2 = '0695' = Goods receipt for inbound delivery => mapped to WHSCON.DELVRY03
The files have different suffixes yet they are not evaluated. SAP-XI just picks both messages and evaluates at runtime whether it has to transform the DLCHDR into a STPPOD or WHSCON IDoc.
Regards
Uwe

IDOC for creation/change of payment terms

Hi all,
We have a requirement to send payment terms information to a non SAP system. I am trying to look for a standard IDOC that contains this information how it can be triggered from OBB8.
If somebody has done it before, please advice. Thanks.
Regards,
Nene

HI nene,
I think there is no standard idoc to send this. You create an RFC and send to non sap.
Regards,
Madhu.

Difference between mastered for iTunes and previous versions?

Is there a noticeable difference between Mastered for iTunes albums and any previous versions? I purchased Bon Jovi's "Have A Nice Day (Special Edition)", and now it has been replaced with a Mastered for iTunes version. Is there any value or noticeable difference if I were to purchase the new version?

One of the inexpensive compilation downloads I purchased on iTunes was terrible, I'd much rather listen to the original mix of " I had too much to dream last night" than the remaster, which destroyed the song completely.
Well, there is really no way to improve on the sound of The Electric Prunes coming over an AM transistor radio!
I guess I'm suspicious of iTunes files in general. I am a dying breed, using separate amps and pre-amps and real speakers as well as Ultimate Ear earbuds and a great car system. The cuts that are engineered for iTunes are mixed for lo-fidelity appliances and just don't sound that good.
There are online download stores that cater to a more audiophile crowd. Check out HD Tracks.

Idoc for Material Change

Hi Experts,
The requirement is to receive a standard Idoc for material change and trigger the material creation process in case the material does not exist.
Secondly, what is the Idoc for material change?
Thanks and Regards,
Ravi

Hi,
Go through the following Steps for Creating IDoc Via ALE
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error.
hope this helps you.
plz reward if useful.
thanks,
dhanashri.

Differences between Dynamixel MX28 servo control and MX106

I have just received a couple of MX106T Dynamixel servos (get to play with torque control!).
Is there a difference between initializing for the MX28 and the MX106?
I can't find any data on that... right now, normally, I create blocks on the block diagram for
"VISA resource name" and "Baud rate" and connect those to the "Dynamixel Motor.lvlib:Initialize.vi" block... which is in turn connected to my actual control blocks.
I know that the MX106T can do torque control as well but haven't explored this. I would very much like to, so if anyone has a tutorial, that would be appreciated.
Thanks.

Hello Slow,
Unfortunately I will not be able to provide any input over the differences between the MX28 and MX106 actuators. If you do not get other replies to this post, it may be worth calling Robotis to see if there is any difference in initializing them.
Here is another discussion post that you may have already seen.. But they discuss an application using multiple actuators from Robotis. The only other resources we have regarding these devices is a DevZone article that details a basic application using them.
Huntington W
National Instruments
Applications Engineer
***Don't forget to give Kudos and Accepted as Solution where it is deserved***

Difference between IDOC Bundling and IDOC Packaging

Hi,
Can anybody please explain the difference between IDOC bundling and IDOC packaging?
Thanks,
Loveena.

Hi,
IDoc Bundling is the changing the occurance of IDoc.
In a scenario If there is a necessitity for changing the Occurance of some segment of the IDOC u have to perform this steps
1.Import the IDoc to XI.
2.Export the IDoc(i.e XSD format) and save it to the local machine.
3.Make changes to the IDoc structure by modifying the XSD file in the local machine.
4.Save it as an XSD file Itself.
5.Import the XSD file in the IR under the External Defination.
6.Use this XSD in your Message Interface/Mapping which is same as IDoc structure but with some changes that u have made.
Go Thru this Blog <a href="/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change Bundling - Trick without BPM</a> BY Michal Krawczyk where the Occurance of the IDoc is changed to 1...Unbounded from 1...999999999 by using the XSD.
IDoc Packing is collecting of IDoc
<a href="/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm of Multiple type IDOCs in BPM</a> BY Pooja
Regards
Santhosh
Remember to set the thread to solved when you have received a solution
[url=Use a Good Subject Line, One Question Per Posting - Award Points; Use a Good Subject Line, One Question Per Posting - Award Points[/url]

Difference between idoc and rfc

what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

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
RFC
Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Difference between IDOC segments starting with E1 and E2

Hi all,
What is the difference between IDOC segments starting with E1 and E2
Thanks

Hi Kajol,
A segment in SAP system is technically implemented as three physically separate pieces.
1. Segment type u2013 the version-independent name of the segment. Standard SAP names begin with E1.
2. Segment definition u2013 contains the fields which represent the data. Its maximum size is 1000 bytes. Standard SAP definitions start with E2 with the last 3 characters implying the version of the segment.
3. Segment documentation u2013 represents the data dictionary documentation for each field in the segment definition. It begins with E3 for SAP provided segments.
For example, E1EDP01 will be your segment type and E2EDP01003 will be your segment definition with 003 indicating its version.By default, the segment type points to the latest segment definition.
Kindly do reward points if you find this as useful.
Regards,
Aswin

Difference between Idoc Adapter and Proxies..

HI XI Guru's,
I am new to XI, I wanted to know what is the difference between Idoc adpater and proxies. When and what should be preffered ?
Warm Regards,
- Priya R

idocs which mean - (intermediate documents) are standard document formats which sap systems use to store as well send data from one system to another. If this is the format in which data has to received by R/3 then you will use idoc adapter in XI. idoc adapter can be used to communicate between systems is with SAP release higher than 3.1.X. Communication using idoc adapter is always asynchronous.
proxies are available for communication between SAP systems with version WAS 6.20 and above. They support both synchronous as well as asynchronous modes of communication. Generally when you are looking at developing new application using WAS 6.20 and above then you can design the interfaces for this new applications in SAP XI and generate the required code for these interfaces automatically in SAP systems using transaction code - SPROXY in the case of ABAP Proxy and in the case of Java proxies the code is generated by SAP XI system itself. You only have to implement these interfaces in your new application. So, basically you have to only worry about building the application and the interface part is taken care by XI itself. you can also look at using proxies when data has to be inserted or fetched from custom/standard tables in R/3 using XI.
,idoc adapter can be used for commuincation between ABAP stacks only but Proxy can be used for both ABAP as well JAVA stack.

Difference between IDOC for creation, change and deletion

Similar Messages

Maybe you are looking for