Message determination process

Hi all,
I have one doubt. Kindly explain.
There are some settings in Material management - Purchasing - Message determination.
Any other settings at company code level other than the above settings.
Thanks & Regards
Ravi

Thanks for your response.
For output type neu, there is no condition records. But for one company code LU01 dispaying two output types neu and cneu.
For remaining company codes BE01, in PO only one output type CNEU.
Even though no condition records for output type NEU, is is displaying in PO,
Why?
Regards
Ravi

Similar Messages

REGARDIMG MESSAGE DETERMINATION PROCESS- OUTPUT TYPES

HI,
IS IT POSSIBLE TO ASSIGN DIFFEREPT FORMS' FORM ROUTINES AND PRINT PROGRAMS FOR THE SAME OUTPUT TYPE?
REGARDS
KRK

Nope, it is not possible. Creation of new message new message type is indeed carried out to have different routines or print programs.

Message Determination & Output Control

Hi all,
What Message Determination & Output Control?
Why we use them , also what are the configuration steps in same?
Please guide me alon with transaction codes involved in it?
Thanks in Advance.
Komal

Hi Komal,
The message determination Process is the process in which you select how you want your output.
You go to T code "NACE" and can see which Application area is activated for which type. Eg. for PO gernally it is NEU. So you can select from here that which procedure and further which sap script or smart form as well as print driver or program is attached to that and can do amendements if desired.
Also you can maintain what are the out put detrmination method attached to that like print, email, EDI , fax etc.
Cheers!!
Biren Agnihotri

Error in Message Determination of GRN

Hello Seniors,
I have done configuation of message determination for GRN by this
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
2. Ensured in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
3. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for GI/Transfer Posting Documents
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, maintain the Output device for all your Plants
7. In MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.(Condition records)
8. While doing MIGO, ensured that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
Now go to MB90 enter the output type as WE01, Tr m as 1, Sort or. 01, Pro.mode as 01, and executed. System outputted all the material documents that has to be taken print out.
BUt after this i did a grn and tried to take prinout in MB90, it is not showing. It is just telling " No messages exist for intial processing". I tried with 2 in processing mode, but still it is showing tha same. Kindly solve please.
Regards,
JanaMM

Not this one the earlier one...
Also did you check whether the GR is properly saved or not...and settigns are done properly or not..which you have given above...
This is not smart form error...assign the smart form again...
ADDED:
Also in the above step ie:
4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for GI/Transfer Posting Documents
Here you shd provide print indicator for GR doc....
Here add for Particular mvt type 101,201,121,311 etcu2026 Maintain the Print item as 1--Material document printout

Error in Message determination for GRN

Hi Friends,
I have tried to configure message determination for GRN. As per the steps in the thread i did. The steps i did are :
GR print out settings
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
Enter the local printer where you want to print your Goods posting document
2. Ensure that in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
3. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for Goods Receipt/GI/Transfer Posting Documents
Here for Particular mvt type 101,201,121,311 etcu2026 Maintain the Print item as 1--Material document printout
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the following--
Select the particular Output type then goto Details
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Printer Determination by Plant/Str Loc, Maintain the Output device for all your Plants
7. Go to MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.
Now the settings are ready for Printing Material doc
8. While doing MIGO, ensure that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
9. Now depending on the setting in 5a, the Matl doc is printed. If it is 3, you have to print it using MB90. If it is 4, it is printed immediately.
After doing this configuration, if i go and execute MB90 with output type WE03, it is telling " no messages for initial processing exist ".
I want to see the GRN document before printing. what shall i do, kindly help me please.
Regards,
Prasath

HI Manish,
As u said, i have unchecked the tick mark in migo and i have posted it. Then i went to MB90 and tried with WE01. still it is showing the same message. Kindly resolve plz. Is there any change i have to do in above mentioned steps.
Thanks&Regards,
Prasath

Message determination and Partner function LS (Logical system) for PO

Hi,
I have worked in the past with vendors (VN) as partner roles in a PO, with the message to create an EDI outpout to Partner Type: LI (Vendor), and this works succesfully.
Now, the idea was to use in EDI, a Partner Type: LS (Logical system) as a receiver of EDI messages (message types: ORDERS) for inbound Purchase Orders to the Partner.
So, we have set up a respective message condition, with Partner Function: LS (Logical System), in transaction: MN04 (Create Output-condition records).
A. When we use ME59N and create a PO with ref. from a PR (created from a sales order), the message determination works well, it reads the condition set in MN04 (condition records for messages), and creates a message (with output type for EDI , medium: 6, and partner function LS: Logical system). Message is created and idoc is sent to partner.
B. When we try with ME21N, ME21 and we create the PO with ref. to the same PR, either by entering manually the PR in the document overview of ME21N or by selecting the PR (without entering the PR number), i.e with date, the message is not created in the PO.
Company code is assigned to purchase organization, and so is purchase organization to plant.
Any idea why there is no automatic message determination in the case of the transaction: ME21N?
There is a single message condition that is to be read for both cases (trans: ME59N and ME21N).
Note: If I try ME21N, and enter the output type and partner (=Logical System), manually, I receive a warning message :
VN006 (Partner XXXX does not exist for partner function LS). If I accept this warning message, then message is saved- idoc is sent.
However you can not assign a partner function LS to a vendor, in vendor master data, because of message CZ 327 (Can not use this partner role).
Anyone with similar experience? Thank you for your advice.

Hi,
I well understand that the receiving partner can be a partner: Vendor (LI).
I have seen that working.
However, in the Partner Profiles (trans: WE20), the receiver was created as a Logical System (LS).
We want the partner Logical system (LS) to receive the idoc for purchase order (ORDERS).
After that, I think that the idea is that the LS can generate an idoc for a sales order creation that will then outbound to another partner. I think that this is the concept.
The issue is that I have seen that the POs created with transaction: ME59N, have received from message determination (trans: MN04) the message with partner LS (automatically), and the idoc of the purchase order (ORDERS) have reached the partner LS.
The question is why the message determination fails when creating the PO from trans: ME21N or ME21, with reference to the PR. Message condition is the same and message determination procedure is the same for both cases.
There is no issue with customizing for the LS in trans: WE20
(Port processing agent is Active for LS and ORDERS have the proper processing code for application EF).
I hope I am helping more with this.

OutPut as a PDF doc for Output Determination process of a PO

Hi
Can I get the OutPut as a PDF document for OutPut Determination process of a PO for a Vendor.
My schema should produce a PDF file and get transmitted to that Vendor as soon i save my PO.
Also can i get any SAP document on this.
Pls help me. Swifty reply me.
cheers
MaruthiRam

Hi,
PO can be sent to using Outlook email or the Internal send within SAP.
Message via E-Mail
Use
You can send purchasing documents to a vendor by e-mail.
You can also send memos to an internal user from within the purchasing document, in which case the recipient can directly access the relevant document when processing the e-mail (executable mail).
Prerequisites
External Transmission
Make the necessary Customizing settings
The SAP system is configured for the transmission of external mails.
The message determination facility has been set up in Customizing for Purchasing.
You have defined a communication strategy in Customizing under Messages Output Control -> Message Types -> Define Message Types for <Purchasing Document> -> Maintain Message Types for <Purchasing Document> on the Default Values tab page, so that if no e-mail address can be found, for example, the system sends a fax.
The following information is necessary:
1.Data
2.Value
3.Comment
Message type:
Communication strategy
E.g. NEU
Choose a communication strategy or create a new one. Via the input help, you can branch to the maintenance function for communication strategies. Choose in the following window.
Enter the necessary data on the Default Values tab page on the detail screen for the message type ().
Processing routines
Medium
Program
FORM routine
5 (external transmission)
SAPF06P (e.g. for PO)
ENTRY_NEU
The entries are identical to those of the print output.
Partner roles
E.g. external transmission/LF
Maintain master data
Message records must have been created through master data maintenance (Purchasing menu). (See Creating Message Records)
Enter the necessary data u2013 for example, role LF (vendor), medium 5 (external transmission) and time spot 4 (send immediately upon saving).
SAP recommends that you work with time spot 4, so that the e-mails generated are sent immediately.
If you work with processing time spot 1 (send via periodically scheduled job), you must schedule the program RSNAST00 periodically for message output, so that messages are generated and e-mails sent.
An e-mail address is stored in the vendor master record.
An e-mail address is stored in the user master record.
Please note that you must also maintain an e-mail address for user IDs with which batch-jobs are carried out.
Internal Transmission
Make the necessary Customizing settings:
You have maintained the Customizing settings for Purchasing under Messages, Output Control -> Message Types ->Define Message Types for <Purchasing Document> -> Maintain Message Types for <Purchasing Document>.
The following information is necessary:
1.Data
2.Value
3.Comment
Message type:
Time-spot
Transmission medium (output medium)
Partner role
E.g. MAIL
E.g. 4 (send immediately upon saving)
7 (SAPoffice)
MP (mail partner)
Enter the necessary data on the Default Values tab page on the detail screen for the message type ().
Mail title and texts
E.g. mail from purchase order
Processing routines
Medium
Program
FORM routine
7 (SAPoffice)
RSNASTSO
SAPOFFICE_AUFRUF
Partner roles
E.g. SAPoffice/MP
SAPoffice/LF
Maintain master data
Message records must have been created for the message type MAIL through master data maintenance (Purchasing menu). (See Creating Message Records)
For more information on the internal and external transmission of e-mails, refer to the Basis documentation under Business Workplace (BC-SRV-GBT).
Further information on external transmission is available in the Basis documentation under SAPconnect and in the section External Sending in the SAP System.
Activities
External Transmission
If you have specified the processing time-spot 4 (send immediately upon saving), the system will immediately generate and transmit a message when you save the purchasing document.
If you have specified the processing time-spot 1 (send via periodically scheduled job), you must initiate the output of e-mails manually.
Result
You see the documents generated in the SAP system under Office ->Work center -> Outbox -> Documents.
Internal Transmission
On the message screen of the Purchasing application (e.g. in the purchase order), enter the message type, the medium (SAPoffice) and the role (MP = mail partner).
Choose Means of communication and enter your text on the following screen (<Purchasing document>: Send with note). Enter the useru2019s first and last names, for example, in the Recipient field.
Executable mail
If you wish to insert a transaction (because you want the recipient to view a purchase order, for example), choose Goto -> Execution parameters. Enter the necessary data, such as execution type (T = transaction), execution element (ME22N = Change Purchase Order), execution system, and the SET/GET parameters (BES for purchase order).
Result
If you have specified send immediately as the processing time-spot, the user will immediately receive a message or document when the purchase order is saved.
The user can view the message sent to him or her via Office -> Work center -> Inbox.
If the document in your inbox is an executable mail, you can click the right-hand mouse button and directly access the relevant purchase order, for example, via the menu thus displayed.
Hope it works...
Regards,
Kiran

PO - Message determination (automatic )

Hi ,
           Can anyone help in setting up the configuration for automatic message determination for same vendor with two different mediums .
like ,
For vendor A ,
o/p type   Medium                    partner       processing    language
NEU          5(External send)        vendorA          4                  EN
NEU          1(Printout)                 vendorA          3                  EN
Both the mediums should automatically pop up in messages when I create a PO .
Thanks in advance ,

Dear Deepa,
After you configure all the setting for message determination in Config
1.IMG>MM>Purchasing >Messages>Output control
2.IMG>MM>Purchasing >Messages>assign output device to purch,group
3.MN04
Make sure the vendor partner function match with the message types-partner function.
Then you'll automatically get the message types generated in PO message after saving the PO document.
Regards,
w1n

Message Determination for GRN again

Hello seniors,
I had configured Output Determination for GRN, it was working fine for a GRN. When i try for next GRN, it is not working. Why is it so, do i need configure any more thing ?
Regards,
JanaMM

Hello manish,
I have done configuation of message determination for GRN by this
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
2. Ensured in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
3. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for GI/Transfer Posting Documents
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, maintain the Output device for all your Plants
7. In MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.(Condition records)
8. While doing MIGO, ensured that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
Now go to MB90 enter the output type as WE01, Tr m as 1, Sort or. 01, Pro.mode as 01, and executed. System outputted all the material documents that has to be taken print out.
BUt after this i did a grn and tried to take prinout in MB90, it is not showing. It is just telling " No messages exist for intial processing". I tried with 2 in processing mode, but still it is showing tha same. But it was workng fine for first time. Even now if i check for that grn it is showing the print preview. but for new grn it is not showing. what could be the reason.
Regards,
JanaMM

Message determination for contracts(Purchase)

Hi ,
I have to recieve the automatic email of contract to buyer , I have created a
condition table with
1)Doctype/Buyer code(Purch group)
2)Assigned table to acess seq
3) Assigned acess sequence to message type
4) Maintained message determination .
I had used transaction NACE and selected application type EV and maintained condition records for Message type with medium 5 and partner as OA .
Now when I create contract , I dont see the message type automatic in the contract and when entered manually , it gives me error saying partner not maintained .
Can anyone suggest me .
Thanks ,

First of all check your vendor has the OA partner function and then go to SPRO-MM-Purchiasng-Messages- output control- prtner role per message type- define partner role for outline agreement
here you have to define for OA partner function then only it will allow you.
. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
For more details, check out the OSS note :191470

Failed Asynchronous Messages still processing

Hi,
Scenario: Asynchronous
QoS: EO
SAP > PI > 3rd Party
I have an almost 1500 failed messages in my SXI_MONITOR SAP PI with an error of 'No Receiver Determination'. I have already solved the issue and the future messages were successful. However, the 1500 failed messages are still being pushed/processed, which is taking up too much memory.
How do you stop these failed messages in processing?
Is there a way that when a failed message already fails, it would stop pushing/processing in SAP PI?
thank you.

Hi,
I think your team mates or BASIS team might have already set a background job for re triggering failed messages in ABAP stack .
If you don't want those messages then you can cancel those in SMQ2/SXMB_MONI.
Regards
Venkat

OUT PUT DETERMINATION PROCESS

Hi
Can any one tell me the steps in out put determination process

hi
this is the standard step by step procedure for Message determination
1. Condition Table
SPRO > Material Management-> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
Ex:
EF---> ZNEU
Select ZNEU and double click on Mail title and texts and go to
EN- New Purchase Order Print Out,
Select ZNEU again and double click on Processing routines,
Select ZNEU again and double click on Partner Roles
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
what are the standard message types for various purchase docs ?
NEU- for purchase order
LPH1-delivery schedul agreement release
LPJ1-JIT delivery schedule release
what are the standard schemas for messages?
RMBEF1- for purchase order
RMBEV1-for schedule agreement
RMBEL1-For delivery schedule release
RMBEA1- for RFQ
what are the standard output devices?
Print-LP01 or LOCL
for other output devices are fax,email,EDI.etc.
Thanks & regards,
Kiran
Edited by: Kiran. V on May 1, 2008 9:58 AM

Customization steps of the text determination processes

Can anybody anybody tell the customization steps of the text determination processes (transaction codes: VOTXN and SO10) of the header of the sales documents step by step in a detailed manner?
Thanks in advance.

Hi Hikmet,
In a business relationship, it is essential that business partners exchange information throughout the logistics chain. In sales and distribution, this exchange of information is supported by texts in master records and documents. You can maintain these texts for one particular customer or define them so that they can be used more flexibly.
Texts can be used in many areas of sales and distribution:
Sales notes for customers
Sales texts for materials
Explanations in order confirmations
Shipping instructions in deliveries
http://help.sap.com/saphelp_erp2005vp/helpdata/en/38/9e9263a1f611d199ad0000e8a5bd28/frameset.htm
reward points if it helps u
with regards
Rajesh
RMD
Posts: 381
Questions: 24
Registered: 1/10/07
Forum points: 690
   Re: Text determination
Posted: Apr 5, 2007 12:42 PM    in response to: raju pusapati       Reply      E-mail this post
Hi,
In a business relationship, it is essential that business partners exchange information throughout the logistics chain. In sales and distribution, this exchange of information is supported by texts in master records and documents. You can maintain these texts for one particular customer or define them so that they can be used more flexibly.
Texts can be used in many areas of sales and distribution:
Sales notes for customers
Sales texts for materials
Explanations in order confirmations
Shipping instructions in deliveries
You can define as many text types as you require (sales texts, shipping texts, internal notes, supplement texts etc.) for master records and documents.
You can take the settings for the texts from Sales and Distribution Customizing under Text control.
Features
You store the texts that are to serve as information carriers in the system and in the output in the customer master record, the material master record, and in the sales and distribution documents. In addition the following processing and control functions are supported:
Texts are proposed from the master records in the sales and distribution documents, if you have made the appropriate setting.
Texts can be copied from a reference sales and distribution document into another sales and distribution document (e.g. from an inquiry into a sales order or from an order into a delivery).
The copying of texts can be made language dependent, if required.
You can change copied texts.
You can integrate standard texts into the sales and distribution documents.
If you want to use texts more than once, you can enter these texts as standard texts and include them in the master record or document texts. If you define standard texts, they are included in the sales and distribution forms when they are issued.
Some standard texts to which you can refer in the sales and distribution documents have been defined in the standard version of the SAP R/3 System.
Notes on Entering Text
You can use standard texts to give notes to the employee entering an sales and distribution document regarding the information he should include in specific header or item texts and the sequence in which he should do it. For example, by including a standard text such as a header note in the sales document, you can make sure that the employee specifies in the first line whether the customer has taken advantage of a sales promotion in his purchase order and in the second line, how (newspaper, radio etc.) he found out about the promotion.
Proposals from the Master Records
The standard text above must first of all be created and then included in a text in the customer master. You can define in Customizing whether this text is automatically proposed from the customer master record in the header note of the document header when you create a sales document.
Standard texts can be proposed in the documents at header and item level in the same way from the material master record.
Create
To create a standard text, proceed as follows:
Select Tools ® SAPscript ® Standard text on the main menu screen.
Enter a name for the text to be created in the field Text name, the indicator ST in the field Text-ID, and the abbreviation for the language in which you want to create the text in the field Language.
Select Create/Change.
You switch to the SAPscript editor. If no standard text has been created with this name, the following message is displayed: Text stands for the language indicator with which you control the language of the standard text. The line in which you make these entries must have the formatting key /: (paragraph format for a command line) in the format column.
Calling Up At the Time of Issue
In Customizing any number of standard texts can be included in the definition of a sales and distribution forms. The texts then appear in the appropriate place in the form when each output is issued.
Further Information
You will find additional information on the SAPscript editor and on INCLUDEs as well as examples online in the hypertext system under the text module name STXD_ED. Proceed as follows:
Select Tools ® Hypertext ® Structures on the main menu screen.
Enter the text module name in the Structure field and in the Language field the abbreviation for the required language.
Select Structure ® Display.
You reach the Display Structure screen.
Place the cursor on the entry that you want to read and select Goto ® Document ® Read.
The content of the text module is displayed on the screen.
Select Back to return to the initial screen.
Also Visit-
http://help.sap.com/saphelp_47x200/helpdata/en/90/758534c960a134e10000009b38f83b/frameset.htm
REWARD IF U FINDS THIS AS USEFUL....
Regds
MM

Error message during processing in BI

1.i am loading the data into infoobject.
2.got error in text data load.
3.master info object have compound obj 0COUNTRY
4.and other normal fields are 0TXTSH,0LANGU,sold-to-party.
5.there is no PSA in this..its direct update to INFOobject.
The error message is:
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Update
Diagnosis
There are duplicates of the data record 2. with the key '3.' for characteristic 1..
Procedure
If this message appears during a data load, maintain the attribute in the PSA maintenance screens. If this message appears in the master data maintenance screens, leave the transaction and call it again. This allows you to maintain your master data.

Hi KP,
In the details tab,
1.under Transfer (IDOC and Trfc):
   Data Package 1 : arrived in BW ; Processing : Error records written to application log
2.Processing (data packet): Errors occurred
   Update ( 0 new / 0 changed ) : Errors occurred
   Error records written to application log
   0TRZONE : Data record 1 ('0000000001D ') : Duplicate data record
   0TRZONE : Data record 2 ('0000000002D ') : Duplicate data record
   Error 4 in the update
3. Process chain error
these are the error details.

A/c determination process - automaticaly flows to the exact plant wise

HI,
I'm posting again, on my blw query,
Pls explain the process abt a/c determination for service po's (with item catelory & a/c assign) during miro.
For example. I have three plants and same tax codes used for all plants and gl numbers are diff as per below. ,
For plant #1 - ESA - 101, ESE - 102, VSE -103
For Plant #2 - ESA- 201, ESE-202, VSE-203
For Plant #3 - ESA- 301, ESE-302, VSE-303
And assume gl is assigned in OB40 (w/o tax code combination) as,
ESA-101 , ESE - 202 , VSE -303 .
While doing miro for what ever plant, it's going and set on appropriate plant g/l nbrs based on trns. key.
Pls tell me how a/c determination process flows automaticaly to the exact plant wise.

Hi ,
For the automatic account posting to different G/L account for different plant---- Group the plants with different grouping by assigning different valuation grouping code. All the automatic account posting config is to be done for each of the valuation grouping code.
Thus the automatic account postings to different G/L accounts happen for different valuation grouping code.
Thanks & Regards,
Amjad

Message determination process

Similar Messages

Maybe you are looking for