This website is not affiliated with, sponsored by, or approved by SAP AG.

Error posting a Good Receipts for Purchase order

Logistics : MM and its sub-modules (WM, IM, PO, LIS)

Moderators: Snowy, thx4allthefish, svetja, Ha Tran

Error posting a Good Receipts for Purchase order

Postby Carolina » Thu Feb 26, 2004 12:20 pm

When we tried posting a good receipt for purchase order (MIGO) the system show the next message:"Field Prof.segmt is a required field for G/L account 001 65200100". The field status group for G/L account have additional account assignments "Profitability segment" obligatory.
We execute the program "RM07CUFA" for the movement type "101", company code: 001 and G/L account: 65200100, and the Field Selection comparison for Profitability segment it's ok.
The transaction OMJJ in Field Selection (Enjoy) not let us add the field "PAOBJNR" .
How I can do that this work ok.
Carolina :wink:

Postby svetja » Fri Feb 27, 2004 4:07 am

OSS note 367813:

The system displays error message KI235 "Account & requires an assignment to a CO object".

This note gives an overview of the possible error causes and the proposed solutions.

Additional key words
MB1A, MB1B, MB1C, MIGO, MI10, goods issue,

Cause and prerequisites
The system found a cost element via the automatic account determination. This cost element requires an account assignment.

The following section explains why the system found the account:

GBB line (offsetting entry to inventory posting)
A GBB line is generated for goods issues, other goods receipts (for example, movement type 501) and for inventory differences.All movement types which work with value string WA01 are affected.You can check the value string using Transaction SE16 for table MSEG (field BUSTW).

Special cases for GBB postings:

Transfer postings:
As of Release 4.5, GBB lines can be created during transfer postings, therefore the GBB account is checked for value string WA04 (see Note 158220)

Goods receipt for subcontract order:
for the withdrawal of the components, a GBB line is created which requires an account assignment (account grouping VBO)

PRD line (price differences)
A price difference account can require an account assignment.Notes 49995 , 215980, 216080, 216094 explain when a PRD posting is created.

KDM line (differences due to exchange rate rounding):See Notes 191927 and 301247.

For which accounting document line (GBB/KBS/PRD/AUM) is the account assignment copied?

The account assignment is only transferred to the line for which the 'Check account assignment' field (T156X-XPKON) is set in the account grouping Customizing (T156X, maintainable via Transaction OMJJ) (see also Note 215931).
In the standard system, field XPKON is only set for the GBB and KBS line.SAP recommends NOT to set field XPKON for other lines (PRD/AUM) because this way not only the account assignment is copied but also the GBB account is copied into the line, which does not make sense for price differences.
Which options do you have of transferring an account assignment for the account?

manual account assignment entry, if the field selection allows it
You can set the account assignment fields to ready for input via the field selection (maintainable via Transaction OMJJ).However, it is not possible to enter the account assignment manually for the following transactions/events:
- Physical inventory (see Note 13423)
- SC components in MIGO Release 4.6B (Note 213318)
A manual account assignment entry is only transferred to the GBB line.Manual entry is not possible for PRD/AUM.

Special stocks E/Q:
As of Release 4.5, for special stock E/Q the sales order or the WBS element is primarily the key for the special stock.So that the sales order or the WBS element is also copied as the account assignment, the field selection for both fields must be maintained (Notes 117596 and 110675).

Account assignment from a reference document (purchase order, order, reservation, material document)
During a goods receipt for the purchase order, bear in mind that field XPKON must be set in table T156X for transaction/event KBS (see above).
For a material document cancellation, check that the original document contains the account assignment (this can be checked using Transaction SE16 for MSEG) and that the field selection of the reversal movement type allows the account assignment.If the material document does not contain any account assignment, the cancellation can be entered by entering the reversal movement type (for example, Transaction MB01, 102) so that the account assignment is copied from the reference document.

Account assignment for automatic goods movements (MB_CREATE)
For goods movements via function module MB_CREATE_GOODS_MOVEMENT (for example, goods movements from LE-SHP, PP, QM), no field selection is checked except for the sales order and WBS element (see Note 365880).The initiator is responsible for transferring the account assignment fields to the function module (internal table IMSEG).

Transaction OKB9: automatic account assignment in CO
If it is not possible to enter an account assignment manually or no account assignment field is transferred to function module MB_CREATE_GOODS_MOVEMENT, an automatic account assignment per cost element or business area/profit center and cost element can be stored in CO.Related notes in CO: 17939, 167733, 41103, 106968.

Substitution in the CO/FI
An account assignment can also be determined via a substitution in CO/FI. See Notes 134484, 136523, 317894.
What can you do if the system displays error message KI235?

Check the account determination:
An account assignment is required not only for consumption postings (GBB) but also for price differences (PRD/AUM).If you are not clear why a posting is made to the account, check the first section 'Cause and prerequisites'.

Certain account groupings should not be assigned to a cost element:
GBB VAX (goods issues for sales orders without account assignment object)
GBB VQP (sampling without account assignment)
Check field selection (T156B.OMBW, OMCJ, OMJA, centrally via Transaction OMJJ):
Check whether the field selection of the movement type is set correctly. At least one account assignment field should be ready for input.For special stock E/Q:see Note 117596. For Transaction MIGO Release 4.6C, the Enjoy field selection should be maintained.
'Check account assignment' field (T156X-XPKON.OMWN, centrally via Transaction OMJJ)
An account assignment is only copied for the accounting line (GBB/KBS) with the indicator 'Check account assignment'.SAP recommends that you do not set the indicator for other lines (PRD/AUM) (see above). Use Transaction OKB9 for the PRD line
Check automatic account assignment (Transaction OKB9)
If no manual entry is possible, an automatic account assignment can be defined.Check that an automatic account assignment is defined for the account in the company code.

Remember that an automatic account assignment is only possible if the account assignment is not a required entry field, as the required entry field check forces you to make a manual entry.

Check automatic account assignment per business area:
- the business area field must be ready for input (field selection)
- the material must have a division (MARA-SPAR)
- the combination valuation area/division must be maintained (T134H)

Check the automatic account assignment per profit center:
- the field profit centers must be ready for input (field selection)
- the material must have a profit center at the plant (ARNB PRCTR)

Problems with profitability segment:
check Notes 70159, 75653, 80466 and 95031

Goods receipt for subcontract order:
Set the field selection of movement type 543 - 546 so that you can maintain a manual account assignment in Transaction MB01 (or Release MIGO as of Release 4.6C) for the components.This is not possible in Transaction MIGO Release 4.6B (see Note 213318). For Transaction MB01, the classic field selection (as of 201) should be maintained for Transaction MIGO the Enjoy field selection.
For a purchase order with account assignment, the account assignment of the main line can be passed on to the components: see Note 68105.

Transfer posting with non-valuated material:
Check that no valuation class is maintained in the material master of the material (accounting view).Also make sure that you implemented Note 158220 in your system.

Known program errors in the following notes:
Note 326856 (errors in CO)
Note 307767 (error in MB_KZVBR_SICHERN, incorrect account modification), enhancement - Note 355627
Note 354804 (errors from Notes 328378 and 354681)
Note 364581 (error for movement type 413)
Cancellation GR from Release 3.1:only via Transaction MB01 102 (note in process)

Check OSS for further notes, I found 9 with keywords MIGO and KI235
Posts: 13946
Joined: Mon Oct 21, 2002 1:42 am
Location: Germany

Postby Carolina » Fri Feb 27, 2004 7:42 am

Hello Svetja,
This information is correct but this is not the problem. The field
G/L account and the movement type has assigned the field "Profitability
segment" correctly (They must be obligatory). But in transaction "MIGO"
doesn't show the field "Profitability segment" for the movement type 101
to make the derivation.
Any other idea???
Thank you very much!!!

Return to Logistics MM

Who is online

Users browsing this forum: Google Adsense [Bot] and 8 guests

This website is not affiliated with, sponsored by, or approved by SAP AG.