Hi gurus need your(s) help,

While running the normal cycle PO->GR->Invoice , users first posted the Goods/service items in the MIRO for the PO & they manually keyed delivery costs secondarily (since there's a another problem behind this i.e, when using RA00 condition type in the PO, after doing GR any changes happens on the PO as an instance on Header Text , PO value totally getting changed automatically and impact is delivery costs not picked on the MIRO. So  delivery costs keyed manually on the invoice)  .

There's is no qty difference for that GR / IR and payment is also done for the vendor. In this case on the MR11 transaction system is showing the delivery costs as a outstanding amount for all the 10 line items , since there's no difference on the freight costs(delivery costs) cant understand why system is showing freight value still to be cleared in the GR/IR adjustment (MR11)???

Added with this, i have simulated similar case on the QA system with same values  in a same sequence ( PO->GR->MIRO(GR value first & later delivery costs) but i couldn't find any value difference showing in MR11 with delivery surplus. Only in PRD system we are facing this.

Could anyone please help me

1. where is the mistake might be?

2,Also want to know what actions need to be taken on this further ?

3. And if MR11 is cleared what will be the impact on accounting side?

awaiting for valuable inputs

Thanks in advance,

Naveen

I'm trying to uncheck all the OWNPR of the FERT materials using the MM17, checking the table MBEW and the field OWNPR. I've tested and saved these changes without any erros, but when I list the materials using SE16N or going to material itself it's still checked.

Any thoughts?

ps: I'm using the Brazilian version

Hi ,

I made Scheduling agreement with LPA agreement type . Maintain the validity , from 1st october to 2nd october - and the delivery created on 2nd oct.

I , created release creation profile and then maintained schedule line for JIT schedule on 2nd oct. and checked by ME84 - that release document was created .

Today , when I checked with ME3L , it displayed that scheduling agreement is still opened position - still showing the open quantity .

After creation of schedule line in JIT and also displayed SA released in ME84 , why it shows as " still to be delivered " ?

regards ,

patel

Hello Experts,

I have a question on GR allocation to parked IR document. My requirement is to have daily batch-job which update GR allocation in the background to parked invoice document.

I searched on SCN and found that function module MRM_INVOICE_ALLOC_UPDATE will perform GR Update Allocation in background(http://scn.sap.com/thread/1377213). I am not sure how this functional module will work. If anyone aware of this function module, or any solution to update parked invoice in the background for every GR.

Thanks in advance.

Regards,

Mayank

Hi experts,

We are trying to cancel the invoice documents which are created in 2006. While trying to cancel, we are getting the errors as below...

1. No reversal possible, reversal value must be reset. (This for one document)

2. Incoming invoice not allowed ORD 600015. (This is because, investment order is assigned in th PO of invoice.

So, please suggest me if any body has solution on it...

Thanks,

Satya

hi, I managed to connect to the vendor catalog through OCI from MM. I need to know where to map the fields of the vendors,to MM fields, i.e. Material Group, Description, etc

Hi Experts,

We have a requirement to maintain the quantity conversions at Condition level for all the items in the STO as below.

In the above screen, all the conditions (YREB, YRED and YREF) have the calculation type as Quantity base.

1. First, let us take YREB. For this condition type, the amount 0.32 EUR is maintained in MEK1. Here, the ordering quantity is 1073.763 TO.

As per the business requirement 1 TO = 1370  L15 as shown the screen shot.

Then, 1073.763 TO = 1471055  L15.

So, finally the condition value is 1471055 * 0.32 = 470737 / 1000 L15 = 470.74 EUR.

These are the required calculation I have to maintain for all the conditions. The above screen shot has given by the user for my understanding about his requirement that what he is looking for exactly. He has manually maintained all the fields as he wants.

But in the normal process, when I am trying to create the STO (within the company), I am getting the quantities from the material master as below.

So, kindly let me know if there is any possibility in the standard to maintain the quantity conversions as in the first screen shot.

Thanks,

Satya

ABSTRACT

IDocs are used in most of the SAP applications for transfer of message from SAP  to other systems and vice versa. A lot of documentation is available on web for IDocs but most of them are technical in nature.  This document is written from perspective of a functional consultant and this will help in dealing with support issues related to IDoc. An effort has been made to capture all the necessary information about IDocs that a functional consultant needs to be aware of.

OVERVIEW

IDoc is an SAP object that carries data of a business transaction from one system to another in the form of electronic message. IDoc is an acronym for Intermediate Document. The purpose of an IDoc is to transfer data or information from SAP to other systems and vice versa.  The transfer from SAP to non-SAP system is done via EDI (Electronic Data Interchange) subsystems whereas for transfer between two SAP systems, ALE is used.

IDoc can be triggered in SAP system or in EDI subsystem. This depends on the direction in which IDoc is sent and is called as Inbound IDoc and Outbound IDoc accordingly. In case of outbound flow, IDoc is triggered in SAP through document message control which is then sent to EDI subsystem. EDI converts the data from IDoc into XML or equivalent format and then sends the data to partner system through Internet.

For inbound flow, EDI converts partner data and IDoc is created in SAP. After successful processing of this IDoc, Application Document is posted in SAP.

EDI STANDARDS AND IDOC

“EDI is electronic exchange of business document between the computer systems of business partners, using a standard format over a communication network”. EDI stands for Electronic Data Interchange.

For transmission of information electronically, two widely used standards are ANSI ASC X12 and EDIFACT. ANSI ASC X12 is a committee formed by representatives of major organizations, government bodies and EDI software companies which defines standards and guidelines for information interchange over EDI. UN/EDIFACT stands for United Nations EDI for Administration, commerce and Transport and was formed in 1985 using ANSI X12 and UNTDI (United Nations Trade Data interchange) as base standards. ANSI X12 describes business document as transactions and each transaction is represented by three digit number e.g. 850 – Purchase Order, 855 - Purchase Order Acknowledgement. EDIFACT describes business document as messages, represented by standard names e.g. ORDERS for purchase order.

IDOC TERMINOLOGIES

IDOC (BASIC) TYPE

IDoc Types are based on the EDI standards and mostly on EDIFACT standards. 

Basic Types (or IDoc Type) defines the structure of an IDoc. Each basic type describes standard IDoc segments, format of data fields and their size. Basic Type also defines number of segments and fields in an IDoc. All the fields that are necessary for transmission of message for a particular business transaction are mapped in different segments. It also defines the structure and relationship of IDoc segments along with mandatory and optional segments.

IDOC EXTENSION

Basic type contains all the standard fields that are necessary for carrying out a business transaction. However, if any additional values are to be sent to the partner then we can make use of the IDoc Extension feature. IDoc extension is extension of basic type and contains additional custom IDoc segments and fields that are not available in standard basic type.

IDOC SEGMENTS

IDoc segments contain the actual data that is sent to or received from a partner. These segments contain the actual values that are sent as part of IDoc transmission.

PARENT AND CHILD SEGMENTS

IDoc segment is termed as Parent segment if it contains its own segments. The dependent segments are called as child segments.

INBOUND/OUTBOUND IDOCS

IDocs sent outside the system are termed as Outbound IDocs and the ones that are received into the system, are called as Inbound IDocs.

IDOC DIRECTION

This signifies the direction is which information is sent and is similar to terminology used in mails. If information is sent outside the system then the direction is outbox when it is received into the system then direction is inbox. In SAP Outbox direction is represent by “1” i.e. outbox and Inbox direction is represented by “2”.

PARTNER

Partner is the Business Partner with which the exchange of information is to take place using IDoc. It can be a vendor or customer or any other system. Depending on the direction of information in which the information is sent it plays a role of either a “sending partner” or a “receiving partner”.

PARTNER TYPE

Partner type/role is used to identify partners within the sap systems. Partner type is KU for customer, LI for vendor and LS for Logical System.

MESSAGE TYPE

IDoc processing involves transmission or receipt of document in the form of a message, each of which represents a document in SAP. These documents can be Order, Shipment Confirmation, Advance Shipping Notification, Goods Receipt, or Invoice.  Message type is associated with Basic IDoc Type (Basic Type) and defines the kind of data or document that is exchanged with the partner.

PROCESS CODE

The process code contains the details of the Function Module that are used for IDoc processing. Message Type can be linked to the Process code.

PORT

IDoc Port contains the information about the way data is sent between the source or target system. The type of port defines the information contained within the port. For port type “Internet” Port will contain IP address of the target system. For port type “file”, directory or file name information is maintained. “tRFC” port contains information about the RFC destination of the target system. For IDoc transmission using ALE “tRFC” ports are used.

PARTNER PROFILE MAINTENANCE

PARTNER PROFILE (WE20)

Partner profile must be maintained for all the business partners to whom we want to send or receive the IDocs. The TCODE for maintaining the partner profile is WE20.

Double clicking on the Partner will show the following screen:

Partner profile contains parameters for Inbound and Outbound processing of IDocs. For each message type we can maintain, inbound/outbound options, message control, post processing options and contact information within Inbound and outbound parameters.

OUTBOUND OPTIONS (OUTBOUND PARAMETERS)

This involves sender/receiver port, Output mode and relation to IDoc type i.e. Basic Type and extension.

MESSAGE CONTROL (OUTBOUND PARAMETERS)

This contains application for which IDoc will be created e.g. EF for Purchase order, the message type of the application that will trigger the IDoc and Process Code that will convert SAP document to an IDoc. For example, if PO is to be sent to the Vendor AXXXXZ, then in the outbound option of the partner AXXXXZ we need to maintain the message type ZXX1 and link it to the Process Code ME10. So when message type ZXX1 is triggered in the PO then an IDoc will be created for the partner vendor AXXXXZ.

Process Code is linked to the Function Module in SAP that converts application data into an IDoc. Standard function modules are provided by SAP for this conversion however these can also be customized as per business needs.

Change Message Indicator indicates whether the IDoc is sent as a notification of change. For example, Purchase Order change messages are sent to vendor using EDI standard message type 860. 

Separate message type should be triggered in the purchase order for PO change. Additional line with change message type must be added in the Message control tab with change message indicator on.

INBOUND OPTIONS (INBOUND PARAMETERS)

For inbound options process code is maintained in the Inbound screen only. IDoc processing can be triggered by background program and triggered immediately.

POST PROCESSING (INBOUND/OUTBOUND PARAMETERS)

In the post processing option we can maintain the workflow details of the users or positions to which an error notification will be sent if an IDoc processing fails.

TELEPHONY (INBOUND/OUTBOUND PARAMETERS)

We can also maintain the contact details in the telephony option.

EDI STANDARD (OUTBOUND PARAMETERS)

EDI standard screen contains the details of the Standard EDI terminology used for the IDoc transmission.

For example, Message Type 850 is an EDI standard for Purchase Order IDoc and is linked to IDoc Message Type Orders.

IDOC STRUCTURE AND RECORDS

STRUCTURE

IDoc structure is divided into Control Record, Data Records and Status records.

These records are stored in the transparent tables in SAP. These are EDIDC, EDID4 and EDIDS.

CONTROL RECORD (EDIDC)

It contains information such as IDoc number, direction, IDoc Status, Basic Type, Message Type, Partner (Sender/Receiver), date and time of creation/update, Interchange File or ISA number,etc.

DATA RECORD (EDID4)

It contains the details of the IDoc segments.

IDoc segment has fields that contain the data necessary for posting the documents.

STATUS RECORDS (EDIDS)

IDoc Status defines the processing status of the IDoc. IDoc statuses are used to track the IDoc and its various processing states. Status Numbers represents IDoc status. Current status of the IDoc is present in Control record.

Initial Status numbers are 64 for inbound and 03 for outbound. Successful status is 53 for inbound and 16 for outbound IDocs.

SENDING AND RECEIVING IDOCS

TRIGGERING AN OUTBOUND IDOC

Outbound IDocs can be triggered from the output message types of Purchase Orders, deliveries, Material Documents, invoices, etc. The following figure shows that once the output ZXX1 of PO XXXXXXX1 is processed an IDoc “000000XXXXXXXXX1” is added/created.

The relationship between the IDoc and the application document can be found in two ways:

1. Relationship tab of IDoc

2. Relationship tab of Application Document, e.g. PO, SO, Material Document, etc.

The initial status of this IDoc will be 30, which after successful processing will convert into status 16.

A successful outbound IDoc will pass through all the above statuses in reverse order (01-03-18-06-12-16). Each status represents an IDoc validation step. If an IDoc passes all the validations it would reach status 16. These different validation steps for outbound IDocs are explained below:

01: IDoc generation successful

30: IDoc is ready to be processed by IDoc Processing job

03: IDoc data is passed to the Port

18: IDoc successfully triggered EDI subsystem

06: IDoc data translated to EDI format

12: IDoc is dispatched successfully to the partner

16: Partner has received the IDoc successfully

IDoc can possibly fail at any of the above steps during validation.

RECEIVING AN INBOUND IDOC

The initial status of an inbound IDoc is 64 and successful status is 53.

Different validation steps for inbound IDocs are explained below:

50: IDoc received successfully in the system

64: IDoc is ready to be processed by IDoc processing job

53: Application document created and saved successfully. The document number can be found by expanding the status node 53

An inbound IDoc goes through all the above statuses in reverse order (50-64-53).

IDOC PROCESSING

AUTOMATIC/IMMEDIATE PROCESSING

In this case, IDoc are processed immediately as they generated or added in the system. The check “Transfer IDoc immediately” is selected in Outbound Options and “Trigger Immediately” is selected in Inbound Option. These checks are generally used when the real time information exchange is necessary between two systems.

MANUAL PROCESSING

IDocs can also be manually processed using the TCODE BD87 in SAP.

PROCESSING VIA BACKGROUND JOB

IDoc processing by background is the most preferred way of processing the IDocs. Following Programs are used from processing the IDocs using background job:

RBDAPP01 - Inbound IDocs

RSEOUT00 - Outbound IDocs

REPROCESSING IDOCS

On the basis of IDoc statuses different programs can be used for reprocessing of failed IDocs. These are given below:

TESTING AND EDITING IDOCS

If an IDoc contains error in the data then such IDocs can be edited using TCode WE02 or WE05. When an IDoc is edited the original IDoc information(backup) is saved in a New IDoc under status 70 (for inbound) / 33 (for outbound). These IDoc stays in the system for reference only and cannot be processed. The status of the edited IDoc becomes 69 (inbound) and 32 (outbound). These IDocs can then be processed using BD87 transaction or batch jobs.

Debugging of IDocs can be done using by copying the IDocs using TCode WE19. WE19 is a test tool for Idocs processing. WE19 copies the existing idoc and creates a new IDoc which can then be modified as per testing needs. The newly generated IDoc can also be processed using BD87.

CONVERTING IDOC STATUS

Report RC1_IDOC_SET_STATUS can be used to change the status of IDoc. Status changes are generally needed to move an IDoc to status 68 – no further processing

SEARCHING IDOCS IN SAP

TCODE WE02/WE05: GENERAL SEARCH

IDocs can be displayed in system via TCODE WE02 and WE05. If IDoc number is not known then  search can be made on the basis of IDoc Date, Direction, BASIC TYPE, MESSAGE TYPE, and PARTNER NUMBER. Partner number can  be found in the Output Messages of the documents.

IDoc search can also be made on the basis of ISA or Transfer file Reference.

TCODE WE09: SEARCHING DATA IN IDOC SEGMENTS

If we are looking for specific information within the IDocs Segments then this can be found using TCODE WE09. This is useful if you are searching for a particular information in similar kind of IDoc within IDoc segments. For example, if you want to search a particular Purchase Order number e.g. 100000001 in multiple IDocs which lies in Segment E1EDK01 of an IDoc under field BELNR. Then the search can be executed in the following manner.

IDOC VALIDATIONS, COMMON IDOC ERRORS AND SOLUTION

Though, the IDoc failure may not be related to any of the above mentioned reasons, the best way to find the IDoc error is to compare the existing IDoc with the good example. Good example IDoc can be easily searched with any of the IDoc search methods as described above.

DOCUMENTATION FOR IDOC TYPES

IDoc documentation can be found using TCODE WE60 and can be helpful to obtain information of the IDoc Type or its particular segment. It also provides information such as  mandatory and optional segments, minimum and maximum number of segments, etc.

GENERAL INFORMATION FOR COMMON IDOC MESSAGE TYPES

The following list gives the Basic Type and Message Type combination for common idocs

ARCHIVING/DELETION OF IDOCS FROM DATABASE

As IDocs grow older they are archived and deleted from the database. Archived IDocs can be viewed using TCODE SARI in Achieve Explorer using archiving object as IDoc. Following are the few programs that are used for archiving and deletion of IDocs from database.

Hello all,

I am experiencing difficulty getting the Multilevel subcontracting functionality up and running.

The Business Function LO_MM_OM_2  is activated and I have customized a Special procurement key 99 in which the Procurement key = F, the Special procurment is L, and the Multilevel subcontracting indicator (V460A-MLSCR) is ticked.

Next I have created two Materials (TEST1, TEST2) both with Procurement key F and Special procurement key 99.

A third Item I created is TEST3 with only a Procurement key F in it.

The BOM is: 1 PC of TEST1 consists of 1 PC of TEST2, and 1 PC of TEST2 consists of 1 PC of TEST3.

Subcontracting Infor ecords and Source lists with fixed Vendors and MRP relevance, all maintained.

Now when I run MRP and a Purchase requisition is created for Material TEST2, nothing special (other than normal) is visible in the Purchase requisiton with regards to the Multilevel subcontracting functionality..
According to the documentation, I should be able to see where the Material TEST2 should go (to the next subcontractor that will make TEST1 out of TEST2).

I ran report RM_MLSC_TRIGGER_MLSC_MRP for the Purchase requisitions in question, but I get the message '06158 No documents found for this selection..'

Also, when I manually create a Purchase requistion for TEST2, nothing happens other than normal.

Does anyone have a clue how I can solve this?

And is ther more documentation out there apart from the one in help.sap.com which is very limited.

Thanks in advance for any clues.

Kind regards,

Bart Jongen

Dear Experts,

My requirement is to generate a purchase requisition form Sales order.

We are able to generate the PR for third party sales. but we need to generate a service PR also.

Please explain the process.

Hello Gurus,

Hope you are all having a great day.

We are facing an issue regarding batch master records.

In MSC2N, when batch deletion flagand batch deletion flag at a plantare marked under Basic data 1 tab,

they are automatically unmarked after saving it.

Can someone please tell me why this is happening?

Please help!.

Thank you.

Ahm.

Hi,

If we refer to an existing material number, the system uses the base unit of measure from the material master record. Material Master does not have any Order unit in Purchasing View.

But we were mentioned Alt Unit of measure in Material master like

1 KG to  1KG

1KG  to Pallet

100 KG to 9 BAG

we were created source list for Material ABC and Vendor XYZ , and created Info record for Material ABC and vendor XYZ and maintained the Price  500 USD per Bag.

Where we create PR for Material ABC, in Valuation tab system taking 500 USD per KG  and Source of supply tab taking fixed Vendor and Info record.

While creation of PO with ref to created PR then system automatically taking Order unit "Bag" and price "500 USD"  from info record.

Here confusion is Why system will not take "Price with Order Unit " PR itself.  as Per Development PR getting Info Price in Valuation Price,

We know the PR will always get the PR value from Material Master and Base unit of measure. if suppose shall we copy Order unit in PR then what will be the Impact, is it copy Oder unit in PO,

PO  copy Order unit from Info

Thanks

Sap

Hi everyone,

I am new here and glad to be here. I was wondering Is it a sound idea to process utilities through the Material Management Module? If yes or no then why so? If I was to create a general standard list of items that should and should not be processed through MM what would I be looking at, please bear in mind i am keep the aviation industry in mind. Looking forward to some insight on the matter. Cheers

Hi, gurus.

In our company we use the reference po.

And one po has several reference po.

But SAP help consist the folowing note:

"You can assign several purchasing organizations to one reference purchasing organization, but each individual purchasing organization should be assigned to just one reference purchasing organization."

Does anyone know why?

Thanks for your replies.

Hello

We are trying to trigger an edi Message at GR using the WE03. But when we Select medium 6 - edi we are not able to trigger any Messages. Is there anything special here, For other output types in NACE we have no problems like this. Our alternativ solution is to use medium 1 and change the printprogram there, but is there any reason that we are not allowed to use medium 6 here?

regards

Ivar

is it now possible to have payment terms at the line item level of a Purchase Order?  if so, how does this impact invoice processing? 

Dear experts,

may I know whether there is any standard SAP report for inbound freight cost based on vendor and PO? if not, which tables we need to use to get the report?  thanks

Dear Experts,

I'll straight go into scenario.

Raw material's received with barrels, carboys which later co do sale.

So my question is that how to take such materials inward without directly mentioning it in item line. (Like BOM)

Also wanted to maintain its stock.

Is it possible to make it happen through BOM or Handling Units?

Hi,

my requirement is system shouldnt allow for goods issue or transfer posting or any other transaction, against reserved quantity of a material.For this i have checked in google got the answer to uncheck the check box for movement, still the system allowing to post the document, i have unchecked the check box in spro-mm-invman&phy inv- default values, still able to post the docyment.

please share your answer with detailed explanation.

Hi,

I created a workflow which open the ME29N with the object BUS2012 and method  singlerelease.

When I release the PO for my level (insert in SPRO – Workflow) I can also release the next level even when I’m not assigned to the release code.  Same effect when I open ME29N directly.

I checked authorization object M_EINK_FRG. It’ s active for ME29N.

What it the reason for it and how can I solve it?

Regards Ralf