Proforma Invoice - IDoc and message type

Hi,
The requirement is to send proforma invoice to legacy system upon creation. We use PI as middleware.
Is it possible to send to proforma invoice data using IDoc?
If IDoc then we have to use message control? Am i right?
What is the process code and what is the basic IDoc type/message type to be used for this?
Thanks for any help.
Cheers,
Srini

Hi Srinivasan
Basic type           INVOIC01 Invoice/Billing document
Message type                   INVOIC     Invoice / Billing document
Process code         SD09
Description          INVOIC: Invoice
Function module      IDOC_OUTPUT_INVOIC
best of lucks and Happy Diwali
Nandu

Similar Messages

ISU Billing/Invoicing IDOCS and Message Type

Hi,
Could any body provide me the list of IDOCS and Message types for Billing and Invocing Module. I was unable find the list across web.

To get the idoc list , u should go to the transaction WE02, and give the search parameter as the basic type of the above said message types..

Diff bet IDOC and Message Types.

What are the difference between IDOC and Message types.
Diff between MATMAS01 ,MATMAS02 and MATMAS03

IDOCs:
- IDOC is an Intermediate Document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data.
An IDOC is created as a result of executing an Outbound ALE or EDI process.
In an inbound ALE or EDI process, an IDOC serves as input to create an application document. When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.IDOC will wait until the Remote System is Active.
Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
basic IDOC type or a customer developed basic IDOC type.
- A basic IDOC type has the following characteristics:
Name : A basic Idoc type can be assigned upto a thirty character name.
List of permitted segments: The segments make up the IDOC structure.
Hierarchy of segments : The hierarchy of segments specifies the physical sequence and any parent - child relationship in the segments.
Mandatory Vs Optional Segments : When used in the IDOC type, each segment has an attribute that defines whether the segment is option or mandatory. Minimum/Maximum range for each segment: It defines the maximum and minimum number of timesa data record corresponding to a segment cn exist in an IDOC.
-Segments : A segment defines the format and structure of a data record. Segments are reusable componets. A segment consists of various fields that represent data in data record.
IDOC Record Types:
1. Control Record : The control record contains all of the control information about an IDOC, this information basically includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC type.
- there is only one control record per IDOC.
- The stucture of the control record is the same for all the IDOCs and is defined by SAP.
- The structure of the control record is defined by the data dictionary structure EDI_DC40. The control record is stored in the EDIDC table.
2. Data Record : Data records contain the application data. A data record has two sections
Administrative Section and a Data section.
- The Administrative section cotain the segment name, client, IDOC number, segment number, hierarchy level information.
- The Data section of a data record is a stram of 1000 bytes where the actual data resides.
- The data record is defined by the data dictionary structure EDI_DD40.
- Data records for IDOCs stored in the EDID4 table.
3. Status Record : Status records are attaced to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a statu code, date and time are assigned.
- Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for inbound processes.
IDOC TYPE IS AN INSTANCE OF IDOC
Message Type: Identifies what type of information transformed between logical systems or partners.Message type is not a local object type , it is transportable.
For different applicatons we have different MESSAGETYPE.
example:
APPLICATION MESSAGETYPE
MATERIAL MASTER MATMAS
VENDOR MASTER CREMAS
CUSTOMER MASTER DEBMAS
MATMAS01, MATMAS02, MATMAS03, MATMAS04, MATMAS05 are all MESSAGETYPES ... FOR NEW VERSIONS LIKE SAP 4.7EE, SAP ECC5.0....we have to use MATMAS05 message type. for older versions like SAP R/3 we have to use MATMAS01.
REWARD ME IF THIS IS HELPFUL

Idoc and message type not getting replicated in the receiver system

Hi
i have created a Z Idoc and didtributed the mode from system A ....I can see the distribution model in system B
However i cannot see the custom zidoc / message type in sys B.. Do i need to create the zidoc again in sys B

Hi Tarang,
at least ou need the required partner agreements and you should have a processing function for inbound IDoc. To implement this, the full definition of IDoc including Segment definition should be present in receiving system.
Just look at standard IDocs and do as they do.
Regards,
Clemens

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

Idoc type and message type

how to find the idoc type and msg type for particular delivery no.
[[i can see the idoc no in vl33n which i have to display in itab.]]

Message type. A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterizes the data sent across systems and relates to the structure of the data called an IDOC type (see below). For example, MATMAS is a message type for Material Master, and INVOIC is a message type for an Invoice (Billing Document). ALE supports over 200 message types in R/3 and about 200 application areas.

IDOC type and IDOC. An Intermediate Document (IDOC) type represents the structure of the data associated with a message type (DEBMAS02 for message type DEBMAS Customer Master, and WMMBID02 for message type WMMBXY Goods Movements), while an IDOC is an object containing the data of a particular message type. IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. For example, an IDOC of type SHPMNT01, message type SHPMNT, will contain data only of one Shipment Document. Generally, the architecture of an IDOC is independent of the message type by virtue of ALEs ability to redefine it for any message type.
Use transaction BD64 or the following menu path to maintain the model: From the IMG (Implementation Guide), Cross-Application Components -> Distribution (ALE) (*) -> Distribution Customer Model -> Maintain Distribution Customer Model Directly -> Maintain Distribution Customer Model Directly.
Hope this helps you....
Regards,
Pavan

Idoc types and message types

Hi ,
Anyone can send what are all the std idoc types and message types are there in SAP?
Coz i dnt have SAP.
Please let me know

The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
An IDoc type consists of the following components:
·       a control record
This is identical for each IDoc type.
·       several data records
One data record consists of a fixed key part and a variable data part. The data part is interpreted using segments, which differ depending on the IDoc type selected.
·       several status records
These are identical for each IDoc type and describe the statuses an IDoc has already passed through or the status an IDoc has attained.
You find various IDOC / Message types in SAP -
http://www.erpgenie.com/sapedi/message_types_masterdata.htm
IDoc Types - Message Types -Accounting Business Processes
IDoc Types - Message Types - HR Business Processes
IDoc Types - Message Types - Logistics Business Processes
Eg.
General       Message types / IDoc types / BAPI
Vendor        CREMAS / CREMAS02
Customer      DEBMAS / DEBMAS03
Accounting   Message types / IDoc types / BAPI
G/L account   GLMAST / GLMAST01
Cost center     COSMAS / COSMAS01
Cost element COELEM / COELEM01

Process code or Fmodule for Idoc type PREQCR101 and message type PREQCR1

hi all,
Iam unable to find the process code or function module for the idoc type PREQCR101 and message type PREQCR1 for inbound process.
help from some one would be a lot appretiated.

Hi,
Go to transaction WE57 and you can find the processing FM and message type that are associcated to the IDOC type.
For process code if it is Inbound check WE42 and outbound check WE41 transactions
Regards
Shiva

Which IDoc Type and Message Type to use for Credit Memo?

Could you guys please tell me which IDoc type and Message Type to use for Credit Memo? Also if possible tell me the process code/ function module.
Will certainly give points for right answer. Thank you for reading.

Hi,
You can use IDoc type FIDCCP02 with message type FIDCC1/FIDCC2 for Credit Memo.
Also you can use this FM FI_IDOC_CREATE_FIDCC1/
FI_IDOC_CREATE_FIDCC2 to generate the IDoc.
Regards,
Ferry Lianto

Difference between IDOC Type and Message Type

Hi, please let me know the difference between IDOC type and Message Type?
Thanks

Hi,
Message type is business name for IDOC you are sending hiding all technical details of the IDOC.
IDOC type gives more technical information about structure of the IDOC.
You will be linking IDOC type to message type while processing IDOC in runtime. You will be specifying message type and IDOC type in WE20 trasaction which says which message will go to which partner whether it is outbound or inbound.
Best Regards,
Krishna

Idoc type and message type for Planned Independent Requirement (PIR)

Hi
Can anyone please give me the information on the idoc type and message type for Planned Independent Requirement(PIR)?
And also the prerequisites to use them.
Regards,
Lohitha
Moderator message: please do more research before asking, show what you have done yourself when asking.
Edited by: Thomas Zloch on May 23, 2011 10:45 AM

Hi,
You can use IDoc type WMMBID02 with message type WMMBXY.
Also please check test program RLMBXY00 to simulate IDoc WMMBID02.
Regards,
Ferry Lianto

Idoc type and message type for inventory

Hi All
What is the idoc type and message type for inventory adjustments? Thanks for any help
Thanks
Ricky

Hi,
You can use IDoc type WMMBID02 with message type WMMBXY.
Also please check test program RLMBXY00 to simulate IDoc WMMBID02.
Regards,
Ferry Lianto

Creation of IDOC with message type INVOIC01

Hi All,
I am trying to create a new IDOC with message type INVOIC01.
When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
The client wants me to create IDOCs with basic type INVOIC01.
Can anyone please help?
Thanks in advance.
regards
Nagarajan

Hi Nagaraj!
I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
Thank You,
Natalija

Outbound INVOIC idoc to partner type LS

Hello,
We are trying to issue outbound invoices( Message type INVOIC / basic type INVOIC02) to a 3rd party who will be doing the billing on our behalf. We are trying to issue an ALE output type to a LS (logical system) partner type and we are receiving a message B1131, that says that partner type LS cannot be used here, only KU and LI partner types allowed.
We can create the idocs if we setup our partner as a KU customer. However, given that we are sending these to a 3rd party system, it seems that we should be using LS. Does anybody know if there is some configuration where we can choose to be able to send an idoc of message type INVOIC to a partner type LS - logical system?
Thanks in advance.
Mark Monroe

Hi Mark,
For your requirement you, create partner profile for LS with following steps :
Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
Message Type : INVOIC
Under Outbound Option u2013 Tab
Receiver Port : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
Pack Size : 1
Transfer IDoc Immediately (Select)
Basic Type : INVOIC02
Cancel Processing After Syntax Error (Select)
Under Message Control - Tab
Application : V3
Message Type : RD00
Process Code : SD09
Hope, your problem will get resolve.
Regards..
Imran

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Proforma Invoice - IDoc and message type

Similar Messages

Maybe you are looking for