Inbound Idoc for material document cancellation

Hello,
Could you update me whether there is any Inbound Idoc type available for material document cancellation (like t.code MBST). I found message type MGBMCR, but it's only allowing me to create the material document like GRs but not cancellations.
/Mallik

To my knowledge, there is no such IDoc. Cancellation is an exceptional situation and should be treated as such. If one needs an IDoc interface for cancellations, I'd have to say there is something very wrong with the business process.

Similar Messages

Need an IDOC EDI STEPS for material document(MB03)

HI ALL,
i need an IDOC for material document. For example, user in SAP make material document (t-code MIGO or MB11), then automatical is downloading outbound IDOC, which contain information about material document.HOW TO PROCESS IT THROUGH EDI .GIVE THE STEPS.

like below you can do your settings
The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
3. After that, assign the IDoc Type to Message Type in WE82.
4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
i. In Message Control Configuration, we'll maintain
a. Condition Tables
b. Access Sequences
c. Output Types
ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.

IS Retail:Report/Document generation for inbound IDOC for Cashier Statistic

Hi Friends,
I have generated an inbound IDOC for Cashier Statistics with transaction WPUK in IS retail.
The IDOC is generated successfully which I can view in POS interface monitor with transaction WPER.
But i dont see any corresponding report or document generated for this successfully posted IDOC.
Is there a functionality in IS retail to generate report/document for successfully posted IDOC for cashier statistics?
Request you valuable inputs on this please.
Regards,
Debraj

Hi John,
Thanks for your inputs.
Could you please let me know how do i activate infostructure S122 to see reports related to cashier statistics after successful posting of IDOC?
Regards,
Debraj

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.

Inbound iDoc for POS message WPUUMS problem

Hello all,
I encountered a strange thing with the inbound idoc for POS with the message WPUUMS.
I've created a new segment with we30 as an extension to the WPUUMS01 like this.
WPUUMS01
--E1WPU01
E1WPU02
ZNRLOT "this is my added segment
E1WPU03
E1WPU04
E1WPU05
E1WXX01
The idocs (external xml files) enter correctly in SAP, when I view them with WE02 al the segments are correctly populated with the right data and they are ready for processing with status 64.
After processing (with the program RBDAPP01 or with WE19 etc. doesn't matter, both uses IDOC_INPUT_POS_SALES_ACCOUNT ) comes the problem:
The Material Document and Billing Document (Invoice) ARE GENERATED WITH ONLY THE FIRST ITEM. I mean that the iDoc has more items(materials) and should generate the material document and billing document with all the items, not just with the first one.
As a conclusion:
1. iDoc is loaded correctly in SAP with all the data in the segments, also in the new segment, and of course has more items.
2. the problem is that after after processing, the generated document material and billing document have only 1 position, the first item from the iDoc.
Any help in fixing this issue will be welcomed.
Traian Mustata
SAP ABAP Consultant

check for the qualifier QUALARTNR. Is it filled accordingly in the z segment? U may also check by debugin the f/n module in we19

Material document cancellation indicator:

Dear Friends,
How to find the Material document cancelled or not based on the Material-doc number.
Is there any straight forward check or status in the Material document itself.
Thanks in advance.
RAMAN.

Hi Jayakanthan
i hope you did't understand my question ,
here is the scenario
I did GR for with 101 movement type and after some time it is cancelled then another material document is created with 102 movement type then by using the same PO i will do GR again with 101 movement type . now i want to differenctiate between these
two 101 documents , if you go to 102 documet there you will get the reference of 101 document number where as
in the cancelled 101 document there is no indication to identify whether it is cancelled or not .when you go the MBSM you will get only
the 102 document
Regards
CVS

Function Module to Generate Outbound IDOC for Sales Documents

Hello Experts,
Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents. Some of the fm's I have come across are the following:
IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
Points will be given for any help provided.
Thanks in advance.

Hi Nagaraj,
I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order. For everyone's reference here is the code:
form process_data.
DATA v_idoc TYPE edidc-docnum.
DATA i_edidd TYPE TABLE OF edidd.
DATA wa_idoc_ctrl TYPE edidc.
LOOP AT i_nast INTO wa_nast.
 CLEAR i_msgs[].
 CALL FUNCTION 'WFMC_PROTOCOL_GET'
 EXPORTING
 cps_nast = wa_nast
 tables
 messages = i_msgs
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
 LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
*--- Check first if there is an IDOC
 IF wa_msgs-msgv1 IS INITIAL.
 CONTINUE.
 ENDIF.
 v_idoc = wa_msgs-msgv1.
 CLEAR i_edidd[].
 CLEAR wa_idoc_ctrl.
 CALL FUNCTION 'IDOC_READ_COMPLETELY'
 EXPORTING
 document_number = v_idoc
 IMPORTING
 IDOC_CONTROL = wa_idoc_ctrl
* NUMBER_OF_DATA_RECORDS =
* NUMBER_OF_STATUS_RECORDS =
 TABLES
* INT_EDIDS =
 INT_EDIDD = i_edidd
 EXCEPTIONS
* DOCUMENT_NOT_EXIST = 1
* DOCUMENT_NUMBER_INVALID = 2
 OTHERS = 3.
 CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
 EXPORTING
 object = wa_nast
 control_record_in = wa_idoc_ctrl
* IMPORTING
* OBJECT_TYPE =
* CONTROL_RECORD_OUT =
 tables
 int_edidd = i_edidd
* EXCEPTIONS
* ERROR_MESSAGE_RECEIVED = 1
* DATA_NOT_RELEVANT_FOR_SENDING = 2
* OTHERS = 3
 IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 COMMIT WORK.
 ENDLOOP.
ENDLOOP.

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear: g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'. "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'. "Direction
* Receiver
case sy-sysid.
when 'DE2'.
 g_idoc_control_record-rcvpor = 'SAPDE2'. "Port
 g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'. "Partner type
g_idoc_control_record-rcvpfc = ''. "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'. "tRFC Port
case sy-sysid.
when 'DE2'.
 g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'. "Partner type
g_idoc_control_record-sndpfc = ''. "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam = 'E1BPACHE09'.
g_edidd-segnum = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
 exporting
 pi_idoc_control_rec_40 = g_idoc_control_record
* PI_DO_COMMIT = 'X'
* IMPORTING
* PE_IDOC_NUMBER =
* PE_ERROR_PRIOR_TO_APPLICATION =
 tables
 pt_idoc_data_records_40 = g_edidd
 exceptions
 idoc_not_saved = 1
 others = 2.
if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
 in background task as separate unit
 tables
 idoc_control_rec_40 = g_idoc_control_record
 idoc_data_rec_40 = g_edidd.
commit work.
endif.
write: / 'Well done!'.

What is the standard inbound idoc for substation management?

Hello Experts,
Can anybody help me to find out the standard inbound idoc for substation management?
The following field are requied to be filled in idoc.
1)Power_Produced(STAGR)
2) Reduction_Power_Consumed(STAGR)
3)Ancillary_Power_Consumed (STAGR)
4)Unit (MEINB)
5) UOM and Date (BUDAT)
If possible please tell me the standard BAPI for these fileds.
Thanks in advance for your help.
Thanks and Regards,
Suresh.

Hi Debo,
What is your exact requirement?
Are you trying to find the standard configurations available for a webdynpro application? then, use t-code SE15 and open the application name and use the tree structure to find out the available configurations under WD application.
sample:
Regards,
Rama

OMX4 - FBN1 - Number range for Material document and FI document

47 - is for FI document number range in Material ledger FBN1. OMX4 gives number range for Material document. My question is how big the number range must be? Since thousands of Materials involved, I couldn't imagin this?
Anybody knows, how to determine the size of no. ranges in Material Ledger configuration? SAP simply says, check no. ranges whether it meets the requirement....
I don't expect an answer again, just check your business, how many transactions would be in a period, which is not quantifiable now?
I would like to understand this from somebody's experience of using insufficient or excessive no. ranges, especially in this area.
Cheers,
Ashok

What is the number range you are using? Year Dependent or Independent?
When you don't know the document number consumption pattern you should use Year dependent number range in both OMX4 & FBN1. Observing this for a month will give a rough Idea and observing for a Quarter will give you a fair Idea and the result for a year gives almost near to accurate consumption of number ranges.
The generation of documents is dependent on the number of materials and Profit centers involved. As much as possibe use Summarization at profit center level when posting to FI. This will reduce the number of documents and line items that are getting generated.

Create transfer order for material document - 4.6C system

Hi Gurus
Can any one provide me the function module or BAPI to create transfer for material document in 4.6c system. I have to give input as supply storage type and bin and destination storage type and bin while execting the function module.
Thank you in advance
Regards
Sarath

Sarath,
Thanks for responding, I finally found my answere via Thread: create transfer order for material document - 4.6C system
Thanks again.

IDOC for Accounting documents

HI All,
Can you help me on this issue?
I have one requirement after create billing documents and Accounting documents ,system should create IDOC for those documents to transfer to other system.
So can you guide me how can be this configuration
Ishikesh

Hello,
You check the possibility of an alternative of this. I believe your requirement is to send the accounting information to a third party system for further processing.
Get the mapping details of the third party system and decide the IDOC type and IDOC segments. Get the help of a technical person, he will guide you propoerly.
Regards,
SAM

Inbound IDoc for WBS data

Hi,
WBS Master Data is stored on an external system (called PRISM).
I need an Inbound IDoc for update in SAP of WBS data sent by external system.
Thank you in advance.
Kieron Kelly

Hi,
Please check the IDOC type : if that doesnt suffice, go with a custom IDOC.
/ISDFPS/PS01
BUS2054001 is a business object that has many BAPI's for processing the WBS data. Check the method and click on ABAP tab for the BAPI/FM names.
Regards
Shiva

Reading Additional info for Material Document (Movement Types 313, 201)

Hi SAP Gurus,
I am currently working on a requirement for Material Document Interface.
The Requirement is as below:
(1) The user creates/modifies a material document using MB01/MB03/MIGO for movement types 313 and 201 separately.
(2) The user maintains additional information by creating a NOTE using the option
SERVICES FOR OBJECT --> CREATE NOTE.
(3) To Print the materail document information.
The Approach is followed is:
1) I have to retrieve the Address for From and To Locations respectively along with document data and display it as Simple List output.
Approach:
I retrieved the data from MKPF and MSEG tables respectively.
Also retrieved the data for FROM and TO locations using table TWLAD and function module ADDR_GET.
(2) I also need to retreive additional information created by the user using the option SERVICES FOR OBJECT --> CREATE NOTE.
Approach:
Request your guidance and inputs to solve the point (2) mentioned above.
I have debugged the SAP Standard tcode MB01, MB03 ,MIGO which have the option SERVICES FOR OBJECT --> CREATE NOTE.
I have also used ST05 to trace the transaction to get a proper solution.
But, i was able to observe that only a table SOOD provides the initial required info only which points to a office document type.
Looking forward to your valuable inputs, so that i can retrieve the data entered using the option SERVICES FOR OBJECT --> CREATE NOTE.
Thanks in advance for spending time and
guiding me to deliver the development on time.
With best regards,
Sudhakar

Hi,
Try this..
TABLES: MSEG.
PARAMETERS: P_DATE LIKE MKPF-BUDAT.
SELECT-OPTIONS SO_BWART FOR MSEG-BWART.
SELECT-OPTIONS SO_MATNR FOR MSEG-MATNR.
DATA: BEGIN OF ITAB OCCURS 0,
 MBLNR LIKE MKPF-MBLNR,
 GJAHR LIKE MKPF-MJAHR,
 MATNR LIKE MSEG-MATNR,
 MENGE LIKE MSEG-MENGE,
 MEINS LIKE MSEG-MEINS,
 END OF ITAB.
SELECT AMBLNR AMJAHR BMATNR BMENGE B~MEINS
 INTO TABLE ITAB
 FROM MKPF AS A INNER JOIN MSEG AS B
 ON AMBLNR = BMBLNR AND
 AMJAHR = BMJAHR
 WHERE A~BUDAT = P_DATE
 AND B~BWART IN SO_BWART
 AND B~MATNR IN SO_MATNR
 AND B~MENGU = 'X'.
The field MENGU might be used to check if the
material movement has affected the stock..
Also I have used posting date = given date in P_DATE..
LOOP AT ITAB.
 WRITE: / ITAB-MBLNR,
 ITAB-GJAHR,
 ITAB-MATNR,
 ITAB-MENGE,
 ITAB-MEINS.
ENDLOOP.
Thanks,
Naren

Problem with mass IDoc for Material Master

Hi All,
Can anyone suggest a solution to work with mass IDocs for Material master?
We have DEBMDM and CREMDM as mass capable IDocs for Customer and Vendor. How do we get mass Material Master IDocs from R/3 in a single XML file?
Also the standard Material repository supplied with SAP MDM 5.5 SP3 doesn't have any XSD definition for MATMDM. Can anyone throw some light on this problem?
Regards
Pooja

Hello Pooja:
The standard way to do it is to generate a single file containing multiple idocs (And for the sake of performance, I suggest you stick to this technique).
In the case of material master, everything is straight forward. In the case of customer and vendor master, when data flows from R/3 to MDM no idoc conversion needs to be performed by XI.
However, for the case of customer and vendor master, when data flows from MDM to R/3, XI needs to separate the data in CREMDM to CREMAS and ADRMAS in order for R/3 to be able to process the idocs; as well as separate the data in DEBMDM to DEBMAS and ADRMAS.
The good thing is that you do not need to worry about all this mappings and conversions in XI. The only thing you need to do in XI is to import the standard business content for SAP MDM 5.5 into XI.
Hope this helps.
Regards,
Jorge.

Inbound Idoc for material document cancellation

Similar Messages

Maybe you are looking for