Idoc type release

Hi All,
When upgrading the system to ECC6.0 will the idoc released number gets changed? ex CHRMAS 46C will change to something like CHRMAS 700?
In other words, Do we have impacts on ALE configurations and idocs as a result of upgrade from 46C to ECC6?
Rgds,
Hk

IDOCs have change from 4.6C to ECC 6.0.
You only get problems if you have not specified "Seg. release in IDoc" in WE20 (specified for each message).
The system will use the new release 600 If this field is blank.
In this case, you will get different segment names etc.
If you enter 46C in the field "Seg. release in IDoc" the system will use the segments for 4.6C and the problem is solved.

Similar Messages

Which Idoc type for Quality release process and Inventory reconciliation/adj. with 3PL

Dear experts,
could you please provide your suggestion on which Idoc type to use for following two scenarios between Client and 3PL vendor (Logistic provider):
1st scenario:
- Products are released in QM in clients SAP. As a result of this action stock status is changed. This information should be sent to 3PL vendor. 3PL vendor receives the information, changes the inventory status in its system and sends confirmation back to the client. Is there any Idoc type that can be used?
2nd scenario:
- 3PL vendor sends stock reconciliation static report to the client. Client receives the report and compares it with own report. Exceptions are reviewed and adjusted upon agreement between Client and 3PL. Once 3PL adjusts the stock, this information is received in Client system and processed subsequently. Any suggestions for an Idoc with Stock reconciliation report and also for stock adjustments?
Many thanks for each idea to everyone in advance.

Hi Ramesh,
thank you for this idea. Unfortunately it seems not be applicable for our system as it is ECC 5.0 and INVRPT Idoc type I can only find in ECC 6.0.
Do you have any other idea or we have to build a new custom Idoc type?

IDOC communication between different basic type releases.

Has anyone run into a scenario where a newer SAP release would like to send a message to a partner with an older SAP release, using a basic type that does not exist in the older system? (eg. DELVRY05 which only exists in release 700)
In this scenario, what is the best practice, other than to have the newer SAP system send an older basic type that does exist in the receiving partner?
Thanks.

Hi,
You can do this by specifying the older release in the partner profile outbound settings (for message type).
Under the "Outbound options" tab there is a field "Seg. release in IDoc type". There you can specify the older release and the IDoc will automatically be depricated when it is received in the receiving system.
Regards,
Gajendra.

IDOC Segement Release vs IDOC Basic Type

Hi there,
we are in an upgrade project and are runing into a general question about idoc creation.
Here is our behavior:
1. We have an reduced IDOC Type in BD53 ZMATMAS based on Messagetype MATMASDI.
2. It has 2 Segements E1MARAM with fields MSGFN MATNR PSTAT and Subsegemnt E1MAKTM with fields MSGFN SPRAS MAKTX.
3. Done the things around (RFC, Partner Profile, distribution model, changepointer ..)
4. In Distribution Model in outbound parameters, added our ZMATMAS.
As parameters we have: Partner type: LS, Message Type: ZMATMAS, Basic Type MATMAS03! and Seg. release in IDOC Type 46B. The Partnersystem is an NoneSAP System.
We are using MATMAS03 because this interface exists since 46B.
Now we send an Material with BD10 and Message Type ZMATMAS.
The Master and Commuidoc are successfull created. In BD87 the commuidoc is an MATMAS03 and has the expected 2 segements E1MARAM and E1MAKTM.
But what we do not expect, if we look into the content of E1MARAM there are ALL Fields which exist for the E1MARAM in release 7.00. Not only our 3 fields MSGFN MATNR PSTAT, or as we second expect only the segemnts that had existed in the segemnt E1MARAM in release 46B of MATMAS03.
The additional fields were filled with the NODATA sign.
My question is: Is it correct that an IDOC with basic type MATMAS03 can have an segement E1MARAM which is formated like the segemntdefinition E2MARAM007 (Release 7.00 / 6.03)?
The difference is definatly the length of the field! 876 in 7.0 vs 757 in 4.6A.
Why is SAP using the highest available segemnt release regardles which basic type we choose?
Isnt this wrong?
Additional infos:
We know that it is not possible to have an IDOC with basic type MATMAS03 with an segement e.g. E1MARA1 which only exists in newer basic type MATMADI if segemnt release is set to 46B in our distribution model.
Failure is: Segment E1MARA1 is unknown in Release 46B/ (correct and expected behavior)
If we are using this scenario with not an reduced message type, we will only find the fields in E1MARAM which are filled with data. (Not all fields of the latest release with nodata)
I traced the MASTER_IDOC_CREATE_MATMAS and hit the function IDOC_REDUCTION_FIELD_REDUCE. As you can see in it, it first checks if the idoc is an reduced message type, and at the end, fills up all fields with the "empty_symbol" which have no data in it. Why is this only happening if it is an reduced message type?
Kind regards
Manuel

Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel

IDoc type could not be determined for the IDoc

I am trying to Post the payment run through the transaction F110.
In the payment run log i get the following message:
"IDoc type could not be determined for the IDoc"
But in fact the IDoc is generated and it is displayed in We05.
I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
Has anybody Idea about why this error is coming and how i can resolve this?
This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
Would appreciate if anyone can please help on the same.
Thanks & Regards,
Narayanan

Hi,
If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
still if you are having any problem
Check in the below path:
IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
2. Assign Release Approval Procedure for Release for Payment
3. Define Users with Authorization to Payment Release
Thanks
Chandra

Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
Thanks,
Veeru.

Hi,
IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
Msg: INVOIC
Basic type: INVOIC02
FM: IDOC_INPUT_INVOIC_FI
Process code: INVF
Thanks,
Kumar

Is it Possible to import an IDoc type from R/3 into APO system

Hi Gurus ,
Could you please guide if we can import an IDoc type from R/3 system to APO system ?? If yes , can you please give the guidelines / step - by - step procedure for this.
Thanks in advance ,
Roseline

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

Issue loading Meta Data for IDoc Type WPUKSR01 in XI Integration Repository

Hi,
I want to load the Meta Data for IDoc Type WPUKSR01 in XI Integration Repository out of BI. Unfortunately, this IDoc is not available in the IDoc List. I checked in BI and the IDoc Type is available in WE60 and WE30. Also, I can load the Meta Data for the Idoc in XI ABAP (IDX2).
Can someone tell me why the IDoc doesn't show up in XI Integration Repository Import Object List?
Thanks in advance.
Best Regards.
Alex

Hi Aamir,
The Idoc is released since Release 30A. I also tried to load the IDoc Meta Data from ERP with the same result: it does not show up in the list.
Thanks anyway.
Alex

Inbound idoc type

i have to do an inbound idoc. first i need to retrieve data from one function module and use the data of that FM into another function module.
so there is a Z function module which has information of both the function module.
i am using the following idoc type
MBGMCR02.
i need to add some more zsegment into it of the other function module the function moduke is WS_DELIVERY_UPDATE 2.
kindly guide please.

Hi Kamlesh,
In we30 you have to create a new Extension idoc type and add the segments. and then from the menu release the idoc type.
Create a new message type ZMBGMCR using we81 or we82.
Create a new Function module to cater to your requirement.
Create a new inbound Process code through WE42 or we41 and attach this function module to the process code.
Link the idoc type, message type and function module through WE57 or BD57
Set the partner profile We20 for the new message type and idoc type and also set the message control tab
Set the port through we20. and give this port in the we21 partner profile.
Create a Customer distribution model BD64 and give the sendor and receiver and from the menu distribute the partner profiles.
Use We19 tcode to test the inbound idoc.
Use we02 or we05 to view the status of the idoc.
The tables for idoc are
EDIDC - control record
EDID4 - Data record
EDIDS - Status record
Some transactions are
SCC4
We20
We21
BD64
we81
we82
bd87
we19
wedi
we02
Hope this helps
Regards
Arun

Receiver determination doesn't work for same IDoc type but in differentSWCV

hi guys,
we have an emergency now. Receiver determination doesn't work for same IDoc type but in different SWCV.Please check below for detail.
1. The process flow is : R/3 IDoc -> XI -> Third party system
2. In previous release R13, IDoc ORDERS05 was imported and used in XI and software component version is R13. And receiver determination was created.
3. Now, in new release R17, IDoc ORDERS05 was imported from R/3 to XI again and software component version is R17. And in R17, the receiver determination created in R13 was used for both old interface(R13) and new interface in R17.
Then we encountered the problem, both interfaces doesn't work now, even we deleted the receiver condition(In R13, IDoc ORDERS05 was sent to system A, and in R17 IDoc ORDERS05 was sent to system B, RCVPRN was used as an condition).
Does anyone encounter this problem? really need and appreciate your help.
-Eddie

information from monitor:
Status Sender Service Sender Namespace Sender Interface
reschedul XXXCLNT100 urn:sap-com:document:sap:idoc:messages ORDRSP.ORDERS05
columns for "Receiver Service","Receiver Namespace", "Receiver Interface" are blank
And then double click records in monitor, go into detail information...
Normally there's lots of setps existed, such as
Inbound Message ( CENTRAL )
Receiver Identification
Interface Determination
Receiver Grouping
Message Branch According to Receiver List
Technical Routing
Call Adapter
But now there's only one setp -
"Inbound Message ( CENTRAL )" existed, no any another setp..., and payload in inbound message looks good.
And in SMQ2, I checked the queue information, found there's an error - "An exception occurred that was not caught." No any other detail information for this error.

RE: Idoc types , Function modules

HI All
What are the generic <b>Idoc types</b> and <b>function modules</b> used for the following objects for SAP R/3 4.7
Invoice Release (inbound)
Payments (outbound)
Purchase Orders (outbound)
Goods Receipts (outbound)
Cost Centers (outbound)
GL Codes (outbound)
Internal Orders (outbound)
WBS (outbound)
Materials (outbound)
Invoices (inbound)
Invoices Blocked (outbbound)
Any help will be very much appreciated
And How do i judge which IDOC types and function module fit my requirement( I mean what are the things i have to keep in mind while choosing idoc types and function modules)
Thnk you
Steve

I have an idea.
Build an idoc from scratch with all the fileds or use the idoc invoic01 and extend it. Comming to function module write a function module that will extract the data from the idoc and will pass the data to bapi BAPI_INCOMINGINVOICE_CREATE( MIRO SCREEN). Please comment on this!!!

IDOC Types and their equivalent messages in EDIFACT and ANSI X12

Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
Regards,

Hi,
Please check these perhaps they may help.
Mapping ANSI X12 to SAP Message Type and IDoc Type:
204 Motor carrier shipment information
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880), EDI - Inbound INVOIC posting configuration
The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is DELFOR01.
832 Price catalog (also 879, 888, 889)
The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04. Outbound processing is supported.
850 Purchase order or order (also 875)
The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
The logical message is PROACT, the IDoc type PROACT01.
855 Ordering or order response (also 865)
The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
For delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
860 Ordering or order modification (also 876)
The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
The logical message is GSVERF, the IDoc type GSVERF01.
862 delivery schedule (FAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is DELFOR01.
864 Text message
The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional Acknowledgment
This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
"22" Shipping OK, acknowledgment has yet to come
"16" Functional Acknowledgment positive
"17" Functional Acknowledgment negative
The status values "14" and "15" are available for the Interchange Acknowledgment accordingly.
Regards,
Ferry Lianto

IDOC Types

Hi all,
can anyone let me know the difference between the 4 IDOC type
MATMAS01
MATMAS02
MATMAS03
MATMAS04
Regards
Simin.R

Hi,
IDoc type MATMAS01 was released in SAP 3.0A and MATMAS02 was released in SAP 3.0D.
There are additional segments added to IDoc MATMAS02 under segment E1MARCM - Master material C segment (MARC).
E1MFHMM - Master material production resource/tool (MFHM)
E1MPGDM - Master material product group
E1MPOPM - Master material forecast parameter
E1MPRWM - Master material forecast value
E1MVEGM - Master material total consumption
E1MVEUM - Master material unplanned consumption
E1MKALM - Master material production version
Regards

ALEREQ idoc type from PI system

Hi,
I have to change the vendor data from Inbound idoc which will be coming from PI system.
but, to get the inbound idoc for vendor we have idoc type as CREMAS05 and message type as CREFET
But,at PI side to send the vendor data, they see the idoc type as ALEREQ01 for message type as CREFET.
Kindly provide me the resolution.
Thanks in Advance.

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

Adding fields to custom idoc type

Hi,
i have a query regarding adding fields to custom idoc type.
To add fields to custom idoc type we are trying to cancel the release from we30, but we are facing error that 'The release of basis type cannot be reset'
When we are trying to cancel release from we31we are facing error 'Error while ressting release of segment z type'.
Kindly suggest the solution to add fields in basic idoc type.
Thanks & regards,
Farheen.

Reason that you are getting these errors is that you cannot cancel
the release of an extension made in previous version . Instead you have to create a new extension.
1.It is not possible to change a segment definition which is released in a
lower release.
2.You must create a new segment definition for the new release e.g. 620 with a new segment
field with the appropriate length.
In transaction WE20, outbound parameters, you can specify
the "segment release in IDoc type" for the communication.
Please read the F1 help of this field for further information.
3.For your own segments you can define a new version of the segment
tcode WE31 -> Add Version
Thanks!

Idoc type release

Similar Messages

Maybe you are looking for