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

Similar Messages

Need help for new message type for PO archiving

Hello All
I have configured new message type ZARR for PO archiving process. After configuring all the steps this condition is not getting picked to by itself. And after maintaing it manually it is giving red flag without any error message. Here I am listing all the step that I have followed for config. Please help me am I missing something or any parameter is wrong.
Steps for new Message Type for PO Archiving
1.     Defined new Table 513 Purch.Org./Plant.
2.     Defined new access sequence Z513 Access Sequence for Archiving.
Following are parameters to the Access Sequence
Access Sequence Number = 21
Table = 513
Description = Purch.Org./Plant
Requirement = 101
Exclusive = Yes (box checked)
3.     Maintain Output Type ZARR for PO
General Data
Access Sequence = Z513
Access to condition (Checked)
Multiple Issuing (Checked)
Program = FM06AEND
FORM Routine = CHANGE_FLAG
Default Values
Dispatch Time = Send Immediately (when saving application)
Transmission Medium = Print Out
Storage System
Storage Mode = Archive Only
Document Type = ARCHIVE
Mail Title and texts
Language = EN
Title = Archiving for Legal Requirement
Processing Routines
Transmission Medium = 1 (Print Out)
Program = SAPFM06P
Form Routine = ENTRY_NEU
Form = ZJ_9H_MEDRUCK
Partner Roles
Medium = Print Out
Funct = VN
Name = Vendor
4.     Fine-Tuned Control: Purchase Order
Oprat. = 1
CType = ZARR
Name = Testing for Archivin
Short Text = New
Update Print Related Data = Yes (checked)
Oprat. = 2
CType = ZARR
Name = Testing for Archivin
Short Text = Change
Update Print Related Data = Yes (checked)
5.     Maintain Message Determination Schema: Purchase Order
Procedure RMBEF1
Step = 100
Cntr = 1
CTyp = ZARR
Description = Testing for Archivin
Requirement = 101
6.     Assign Schema to Purchase Order
Procedure RMBEF1
7.     Define Partner Roles for Purchase Order
Out. = ZARR
Med = 1 (Printout)
Funct = VN
Name = Testing for Archivin
Name = Vendor
8.     Test Condition Maintained in MN04 (Master Data)
Purch. Org. = 0001
Plant = 24
Partner Funct = VN
Medium = 1 (Printout)
Date/Time = 4 Send immediately (when saving application)
Output Device = HUL1
Storage Mode = Archiving only
Thanks
Ankit

the problem is the Exclusive = Yes indicator in the access sequence.
Your other message has this exclusive indicator as well.
so if the first message is found, then no other message wil be determined
to allow several messages in one PO, you must not set this exlusive indicator

Multiple message types for an idoc type

Hi all,
I created one custom idoc type with six segments. I heard that one idoc type can have any number of message types
if it is so pls tell me how to assign these two message types for my idoc .
i want to create multiple message types because i want to send same idoc type to diff legacy systems.
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?

Hi Kunal,
Below are my thoughts from a design perspective,
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
Before you look upon the no. of message types you need, i guess you need to look at the business requirement. Per your requirement you want to send send two sub sets of data. The first subset in the first 3 segments and other three segments for the second subset of data.
Is the structure of the first subset of data similar to the second subset If not, better to create two IDOC Types. If they are similar, then create one IDOC Type with three segments and have two message types for each subset of data.
For Ex: ORDERS05 is the IDOC type for Orders, this IDOC type provides capability to carry data related to any type of orders
but the action on the data is facilitated by the message type like ORDERS for create, ORDCHG for change, ORDRSP for Order response etc.
OR
Are these two subsets of data related to each other, if yes understand the relation? If not related at all then you might be better of creating two separate IDOC Types.
Like in the above example A purchase order is related to a sales order so you can use the same IDOC type, but in case of a order response and ASN that data sent is different and hence you will need different IDOC types (even though a SO is related to a DN).
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?
The above again depends on the how tightly/loosely coupled are the data sets, you can have just one program and have a simple case statement on the message types or have two different programs.
You will also have to consider points like, if any of the subsets is more prone to more change in terms of the structure and associated business logic. If yes, then you might want to keep the programs separate to reduce work on regression testing etc.
I am sure you will receive more inputs from the experts on the forum and the list of points to look for will get longer , so understand the requirement, dependencies and if you have any specific questions you could post it on the forum.
Regards,
Chen

New Message type for Sales orders

Hi,
We have the message type is ORDSRP(ORDERS05) and Function module IDOC_OUTPUT_ORDRSP for the sales orders.
We have lot of custom fields to be added to the IDoc.
Can any one suggst if it is better extending the current message of create a new one.
Thanks.
Rohita.

Hi Rohita,
Instead of changing the standard domain, You have to make the changes in the User Exit.
Say Qualifier 001,002,003 were already there in the domain.
001--Purchase Date
002--Delivery Date
003--Ordered Date
In the user exit u have to just add the segment and the qualifier without making any changes to the Standard Domain.
These Qualifiers are just like other variables and u can add whatever values to them that u want..
You can add Qualifier 004 for Trnasportation Date or Goods issue date and have to communicate the MiddleWare informing that date with this Qualifier will be Transportation Date and they will do the mapping to the corresponding field in other syste.
You can have as many message types as u want for the same IDoc type. There is no harm in having multiple message type. And u dont need to change the standard domain. It can be done without changing the domain.
If u analyse the FM closely u will realise that they have done coding for those values in the domain.
So instead of adding it to domain u just have to do the coding for this new qualifier.
Revert back if u need any help on it.
Thanks...
Message was edited by:
Utsah Garg

Message type for generating IDOC for SUBCONTRACTING PURCHASE ORDER

Hi All,
I have to generate IDOC for PO creation or change .
I am using IDOC_OUTPUT_ORDERS and IDOC_OUTPUT_ORDCHG.
The messagetype.idoctype I am using is ORDERS. ORDERS05 and ORDCHG. ORDERS05.
Now the confusion is regarding whether this message type will work in case of SUBCONTRACTING PURCHASE ORDER as well ?
As I have gone through some websites and came to know that I will have to use PORDCR1.PORDCR102 specially for subcontracting.
And programs we need to use is BUS2012_ICH_R3 instead of RSNASTED and Form Routine SEND_PORDCR1 instead of EDI_PROCESSING.
Purchase Order Collaboration scenario - Not generating IDOC in ECC
http://www.erpgenie.com/faq/edi_purchasing.htm on this site question no 8.
Subcontract PO IDOCs
I hope your experience will help me .
Please reply ASAP.
Edited by: uttam27 on Dec 4, 2011 1:47 PM

There is a generic function to create change pointers for all message typs - 'CHANGE_POINTERS_CREATE_DIRECT'. This is triggered only if you configure your message type to create change pointers from BD50.
Once you activate it do any change to orders you can see change pointer tables BDCPV filled. Then BD21 will read the changes and generated outbound idocs accordingly.

Creation of new document types for document splitting rules

Hi experts,
We have copied from existing SA document type to new document type.
In standard SAP SA document type - define document splitting rule, we have select "NO INHERITANCE OF ACCOUNT ASSINGNMENT", when posting the GL document SA document type without mapping partner profit center,system is control the derive the partner profit center.
Our requirement is copied from existing SA document type to create a new document type - we have created the new dusiness transaction variant and we have map the "classify document type to document splitting rule " and we have selet the "No inheritance of account assignment" while posting in FB01 GL document with out mapping partner profit center system is not control the " derive partner profit center".
Could you please assist us as soon as possible
Thanks ,
Sreenivas
Edited by: sapfico.srini12 on Jan 16, 2012 4:37 PM

Hi,
In order to create a document type for a purchase requisition use the path
spro-materials management - purchasing--purchase requisitions --define document type
in that screen you select the document type you want to copy to create your document type and perform the action.
if you want to change the screen/field selection for your document type select the field selection key (if you select the document type as NBB the field selection key will be NBB.,and go to the screen and change the field status.
Hope this will be suffient for your requirement.
Regards,
Raghu.

Creation of new movement type for Goods Receipt

Is it possible to create a new movement type same as 101 (goods receipt)? We need to create a separate movement type of 101 for the purpose of separating G/L account to be used for local and importation purchases. Or is there any other way to separate the G/L account for GR of local and importation purchases without creating a new movement type?

You can create new Mvt type by copying Mvt type in OMJJ trxn ..
Please follow the following steps
Check whether you can use the preset movement types.
If not, define new movement types as follows:
1. Once you have carried out the activity, the system displays a dialog
    box for field selection. In this, you can restrict the movement
    types you work with to various fields. To copy a movement type,
    select the field Movement type and choose Continue. The dialog box
    Define work area appears.
2. In the dialog box Define work area, enter the movement type you want
    to copy in the From: field. In the To: field, enter the name of the
    new movement type you want to create. To go to the overview of the
    selected movement types, choose Continue.
3. Select the movement type you want to copy, and choose Edit -> Copy
    as.
    Overwrite the selected movement type with the new movement type
    (beginning with 9, X, Y, or Z) and copy all dependent entries.
    The system copies all control indicators from the reference movement
    type to the new movement type.
4. Check all views for the new movement type and, if necessary, change
    the control indicators. Please note that some views have a detail
    screen.
5. Copy the reversal movement type and enter it in the view
    Reversal/follow-on movement types.
6. Save your settings.

Logical Message Types for MM IDOCs

Hi,
My Client is on ECC 6.0. They are using a third party system and the information coming from that system has to create a PR, PO, GR, GI, Invoice receipt(MIRO) and Vendor Invoice (FB60) through IDOC's, which are inbound to SAP.
What are the Logical Message Types we can use to transfer all the data into SAP. Also, how to look at the fields in the IDOC to check if all the required fields are available in the IDOC.
Thanks,
Randy.

I'm not an expert but as per my knowledge these are the IDOC types and you can check the IDOC structures using we30.
Purchase Requisition: PREQCR101
Purchase Order: ORDERS01
Post Goods Issue: MBGMCR01 / MBGMCR02
Goods Receipt: WMMBID02
Invoices: INVOIC01

Message type for idoc PROJECT01

Hi ..
How to send a PROJECT01 idoc from one r/3 to another or third party system.What is the message type for the idoc and what are the configurations required.
Tharun

Hi Tharun,
The Message Type for the basic type PROJECT01 is PROJECT.
Using this basic type u can send only project and wbs related Information using BAPI.
For Configuration the steps are as mentioned below.
1.Define Logical Systems in sender and receiver.(SALE)
2.Assign Client to Logical system in the respective systems.(SALE)
3.Create RFC Destination.(SM59)
4.Create a distribution model .(BD64)
5.Click on Add Bapi, specify your sender, receiver the Object name as <b>ProjectDefinition</b> and the select the Method of your interest.
6.Generate Partner Profiles in the Sender System.
7.Distribute the Model to the receiver.
8.Generate Partner Profiles in the Receiver System.
Hope this helps you..
Let me know incase u have any questions.
Thanks & Regards,
Vanita

Creation Output Message Type for Scheduling Aggrement

Hi,
Please share the detail configuration for the Output message type for scheduling aggrement, i need to use ALE IDoc so that i can send this SA to SRM system.
Regards,
Pankaj

Hi,
Output determination process for Scheduling aggrement.
SPRO-IMG-Material Management-Purchasing-Messages-Output Control-
1)First create condition table based which becomes condition record for accessing the data.
2)Create access sequence to access the data or search the based on the conditoin record in sequence of the condition table.
3)Define your message type like print,fax etc.
Maintain the conditon record for the MN07 for the output type which new one you created.
Regards
Ravi Shankar.

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

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

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

Idoc Message type for Customer Change XD02

Hi All
As per the business requirement, we need to have inbound interface to ECC system, in which we will add more partner's to the existing customers.
I tried posting Idoc thorugh WE19 using message type DEBMAS and basic type DEBMAS06. It is creating the new partner which is part of the idoc but it behaves like a refresh, i mean the already existing partners are getting deleted.
Tried to find the relevant message type for XD02 but did not find other than DEBMAS.
Can anyone let me know how to acheive this.
Following are the segments am passing.
E1KNA1M :
MSGFN     4
KUNNR     1234
ANRED     /
BBBNR     0
BBSNR     0
BUBKZ     0
KTOKD     /
LAND1     /
NAME1     /
ORT01     /
ORT02     /
PSTLZ     /
REGIO     /
SORTL     /
SPRAS     /
STRAS     /
TELF1     /
LZONE     /
UMJAH     0
JMZAH     0
JMJAH     0
UMSA1     0
HZUOR     0
CIVVE     X
SPRAS_ISO     EN
E1KNVVM :
MSGFN     4
VKORG     1
VTWEG     1
SPART     1
KALKS     1
AWAHR     100
ANTLF     9
KZAZU     X
LPRIO     1
VSBED     1
WAERS     USD
VWERK     ABCD
UEBTO     0
UNTTO     0
PODTG     0
E1KNVPM :
MSGFN     4
PARVW     RE
KUNN2     1010
PARZA     0
After execution, i am getting IDOC status 53 with message "Changes have been made".
Thanks & Regards
Madhu K

Hi Madhu,
/thread/2051526 [original link is broken]
Same post in abap general.
Regards,
Madhu.
Edited by: madhurao123 on Oct 4, 2011 11:59 AM

Equivalent Idoc message type for EDIFACT BANSTA

Hi Experts,
I am trying to find out the equivalent IDOC message type for EDIFACT BANSTA. The purpose of the message is to show the item level statuses for a particular payment batch. There are lot of references about FINSTA01, however, this is for account level status response.
If anybody know the equivalent idoc message type for EDIFACT BANSTA, kindly let me know.
Thanks in advance.
Regards,
Ravi

Thanks raja shekar. I posted this thread in ABAP development forum.

MB1B transfer posting Idoc/Message type for outbound and inbound

Hello All
Can anyone tell me the idoc/message type for movement type 313 outbound and 315 inbound to SAP. This is for MB1B Enter Transfer Positing.
Thanks
Ricky

Its WMMBXY

IDoc Message Type for VL09

Hi,
Is there an IDoc message type for VL09 (Reverse Goods Issue) for Delivery. Do let me know please.
We are using an ECC 6.0 system (WebAS 700)
Regards,
Aditya

Hi,
You can use this message type MBGMCA, IDoc type MBGMCA01 and process code BAPI.
This process code will call FM IDOC_INPUT_MBGMCA to reverse good movements with MB_CANCEL_GOODS_MOVEMENT.
Regards,
Ferry Lianto

Creation of New Message Type for Extended IDoc

Similar Messages

Maybe you are looking for