Table T169P

while doing migo i am getting an error msg. Check Table T169P: entry "XXX"does not exist. .....?

This is because of Company code settings not done in Logistics Invoice verifications
Go to Spro
materials management>Logisti Inv Verifcation>
do the settings for Invoice blocks, Tolerances, then Incoming invoices.., Indicator stochastic Block
for seeing more details on this go to se11> enter T169P > then go for display u can see the fileds what are all you need to update. just chk and update that
your problem will be solved
reward if useful
R/

Similar Messages

Table T169P: entry 1000 does not exist

Hi,
While doing the Goods Receipt, against Purchase Order, the following error is coming:
Table T169P: entry 1000 does not exist
Please guide.
Regards,

Hi All,
Issued resolved.
Table 169P refers to Parameters, Invoice Verification. This is available under
IMG>Materials Management>Logistics Invoice Verification>Incoming Invoice>Set Check for Duplicate invoices.
Regards,

Check table 169p: entry bal does not exist

hi experts,
this error (Check table 169p: entry bal does not exist) is comming while my end user is doing goods receit in t code MIGO .bal is the name of the com code and business area
thanks&regards
surya varma

Hi,
The message is issued as you have not yet maintained the parameters for invoice verification in company code BAL
Please use transaction OMRG to maintain table t169P.
Best Regards,
Arminda Jack

Check table 169P: entry 9849   does not exist

Check table 169P: entry 9849   does not exist
Message no. M7001
Diagnosis
In table 169P the entry 9849   is missing.
Procedure
Make sure your entries are correct.
If table has not been maintained correctly, please inform your systems administrator.
Plese tell me how to rectify this error
regards
Satish

Hi,
Please use transaction OMRG to maintain table t169P. Apparently you are
missing an entry for company code 9849.
Please assign points if it useful.
Regards
Ravinagh Boni.

MARV TABLE

How to assign a company code to MARV Table in SAP MM?

Hi,
Why you want to entry company code in table level .....that to MARV table. MARV table generally used to check who and chnage log of posting period.If it is testing server you do the trial process by updating MARV table but not advisable in production server and before performing this action to touch MARV table please contact SAP and take advice.Consult ABAPer also for help.
NOTE:
What transaction you are doing and want to update table, check table T169P for entry of company code.
Regards,
Biju K

Error during MIGO

Dear all,
while doing MIGO for the PO i am getting following error
"Check table 169P: entry PICT does not exist
Message no. M7001"
In table 169P the entry PICT is missing..
PICT is my compnay code.
Also in GR Excise tab " BED,SED, AED for excise item is zero. "
But in PO in INVOICE tab against tax code system is showing the correct values of BED.
wHERE Should i check for same.
Best Regards,
Venu

Hi,
Go to SPRO > MM > Logistics Invoice Verification > Incoming Invoice > Here configure following
- Tax Treatment in Invoice Reduction
- Maintain Default Values for Tax Codes
- Configure How Exchange Rate Differences Are Treated
- Configure How Unplanned Delivery Costs Are Posted
- Edit PO Supplement Text in Invoice Verification
- Activate Direct Posting to G/L Accounts and Material Accounts
- Set Check for Duplicate Invoices
And then check Table T169P, it will have aal the parameters mainatined for Invoice verification for compnay code. Then do MIRO.
Aslo go to OBCL and mainatin input tax code of Zero % for compnay code.

Treatment of exchange rate difference- company code not appear in the list

Dear guru,
I am configuring the treatment of exchange rate difference (SPRO> MM> LIV > Incoming invoice> configure how exchange rate differences are treated). However,the company codes that needed to be configured are not appear in the list. Please note that in the config screen, dont have the option of "New entry", we only set base on the list of existing company codes.
Also, please be noted that we configured accounts for KDM, PRD in OBYC already
Appreciate your respond.
Thanks and best regards,
Hong

Hi,
Check in table "T169P" & "T169V", whether your Co. code exists or not? If not then maintain following config settings.
SPRO > Materials Management > Logistics Invoice Verification > Incoming Invoice
> Maintain Default Values for Tax Codes (After maintaining this entry by "New Entries", it will start appearing for following options)
> Configure How Exchange Rate Differences Are Treated
> Configure How Unplanned Delivery Costs Are Posted
> Edit PO Supplement Text in Invoice Verification
> Set Check for Duplicate Invoices

Error in GOODS Receipt .Integreation Config

hi,
When i am configuring the Integration with MM in GOODS RECEIPT .It throws this Message .Check table-169P entry XYZ does not Exist .Here XYZ is my company code .
Pl..Thanks in Advance
Satish

Hi,
You need to maintain the company code in this table.
Procedure:
Use SE11, data base table T169P and click display
Next screen, click " contents" icon in the application tool bar
Next screen, give company code and execute.
It will do.
If you have autorisation problem (SE11)check with BASIS people.
Regards,
Murali

Special GL - F-65 Check duplicate invoice

Dear All,
I have a requirement, we use F-65 and apply BTE Process "00001110" DOCUMENT POSTING: Check on invoice duplication
to check against duplicate invoice for Reference + Currency + Vendor Code. That is OK.
But now, user would like to check special GL posting too. But it seems cannot check it. Trace the program, it will not
call Process 00001110.
Can anyone help on this ?
Thanks.

Unfortunately, standard SAP only allows a fixed duplicate invoice check in F-43/FB60. Unlike LIV, you cannot configure which fields get checked.
Use BTE 00001110 (process module) and build a function that reads the MM LIV duplicate invoice configuration (table t169p). The BTE will be called appropriately for F-43/FB60. I developed and implemented this a while ago and it works great.
I hope this is useful.

Check Duplicate Invoice in FB60 and F-43

Dear Experts,
I want to check duplicate invoice in FB60 and F-43. Normally, system only check if company code, vendor, currency, reference no. and invoice date are match. If I only want to check for company code, vendor, currency, reference no. are match except invoice date.
Anybody can help?

Unfortunately, standard SAP only allows a fixed duplicate invoice check in F-43/FB60. Unlike LIV, you cannot configure which fields get checked.
Use BTE 00001110 (process module) and build a function that reads the MM LIV duplicate invoice configuration (table t169p). The BTE will be called appropriately for F-43/FB60. I developed and implemented this a while ago and it works great.
I hope this is useful.

MIGO-Thirdparty sales

HI Gurus,
in Third party sales while iam working on MIGO, once i enter the PO number iam getting the error like " check table 169p for plant 'XXX' ".
what could be the reason for getting this error and how can solve the problem,
please suggest
cheers

Hi PS
So go to SE11 and give table T169P and execute and click on copy or create icon and then copy from the existing plant data to your plant . This happens sometimes because while copying plant , some data wont get copied
Regards
Srinath

Enhancement/Exit to flag Blocking Reason (RSEG-SPGRS) in MIRO

Hi,
I am facing a problem right now since I cannot find any exit/enhancements that can flag the Blocking Reason (RSEG-SPGRS) in transaction MIRO.
It is so much appreciated if you can help me to identify which exit/enhancement should I use.
Thank you in advance.

Hi,
This is what i´ve found out:
field RSEG-SPGRS is flagged within fm MR_BLOCKING_REASON_S.
And this field is flagged according to the criteria set in tables:
T169P (Parameters, Invoice Verification)
T169G (Tolerance Limits, Invoice Verification)
...etc.
Have a look at this fm.
If you do a "Where used" search of this fm you will see that is is called in:
Include LMRMPF1L
Subroutine SPERRGRUND_S
if you have a look at this subroutine you will see that there is an exit there:
CHECK PX_DRSEG-SPGRS NE SPACE.
SY-SUBRC = 0.
CALL CUSTOMER-FUNCTION '001'
       EXPORTING I_RBKPV = PI_RBKPV
                 I_YDRSEG = PX_DRSEG
       EXCEPTIONS CALL_FAILURE = 001.
CASE SY-SUBRC.
    WHEN 001.
      MESSAGE E271 RAISING PARAMETER_ERROR.
ENDCASE.
The exit is EXIT_SAPLMRMP_001.
then there is call to fm MRM_TOLERANCE_CHECK
within this fm there is an exit:
*------- Customer Exit ------------------------------------------------*
CLEAR: CHK002, SY-SUBRC.
CALL CUSTOMER-FUNCTION '001'
       EXPORTING I_BUKRS = I_BUKRS
                 I_TOLSL = I_TOLSL
       IMPORTING E_WERT1 = X169G-WERT1
                 E_XW1JA = X169G-XW1JA
                 E_WERT2 = X169G-WERT2
                 E_XW2JA = X169G-XW2JA
                 E_PROZ1 = X169G-PROZ1
                 E_XP1JA = X169G-XP1JA
                 E_PROZ2 = X169G-PROZ2
                 E_XP2JA = X169G-XP2JA
                 E_CHECK = CHK002
        EXCEPTIONS CALL_FAILURE = 001.
This exit is EXIT_SAPLMRMC_001
And within fm MRM_TOLERANCE_CHECK there is the possibiliy of an implicit enhancement.
question: why trying to flag field RSEG-SPGRS when you have tolerances available?
Best regards.

Double invoice entry at the FI Level

Where do I go in the FI level not to allow double invcoice entry.
Thanks
AG

> Csaba Soltesz,
> Could you explain both:
> How do I set up the FI_DUPLICATE_INVOICE_CHECK
> validation and also how to do it for MIRO
> transactions.
> I would appreciate feedback.
> Thanks
> AG
Hi Ana,
sorry for the late reply.
For the FI check, there is no specific setup. Only thing you need is to set the corresponding flag in the vendor master (company code view). Then, if the prerequsites are met (see below), a warning message will appear.
How the check is working in FI? (ie., FB01, FB60 or similar, NOT logistics invoice verification, for LIV, see below):
1. Is this a vendor line (account type K)?
2. Is the flag set in the vendor master?
3. Is the line item sales relevant (based on the posting key, e.g., 31 is sales relevant, 25 is not)
4. Is this a normal document? (not recurring, parked, clearing, sample doc)
5. Do we know the document currency?
6. Do we know the document date?
7. Is the amount in document currency <> 0?
If the answer to all of the above was YES, then the check is carried out. What is actually checked, is table BSIP. Every time when you post a document meeting the above criteria, BSIP will be updated. Next time the BSIP entries are checked.
And here the checking rules:
IF the reference field (BKPF-XBLNR) is filled in, then the message is issued when there is a BSIP record already with the same:
- company code
- vendor number
- document date
- reference
- document date
- D/C indicator
IF the reference field is NOT filled in, in addition to the above, the amount in document currency is also checked in BSIP, so that field must match too in order to get the message.
The message is F5 117 and the type can be changed in customizing (view V_T100C) as usual for customizable messages.
The above list also answers another question in this thread: NO, it is not possible to check it cross company code. I.e. if you have entered an invoice for company code A, then you can enter the very same invoice for company code B, there will be no message at all. You need to create some validations (transaction OB28) to achieve this. The standard check is working within the same company code only, see the list above.
Now, that was the pure FI thing, how about Logistics Invoice verification (MIRO, etc.). Here, you have some more configuration options. The function module called here is MRM_FI_DOCUMENT_CHECK.
The check in Logistics Invoice Verification is carried out only if the below criteria are met:
1. Reference field is filled in (!!!!! extremely important!!!!)
2. This is an invoice (and not a credit memo... see RBKP-XRECH must be X)
3. The vendor number is known
4. The flag is set in the vendor master (company code view).
The check is made against BSIP again, but WHAT exactly is checked, i.e., which fields must match, is customizable. In table T169P, you can tell the system which fields you want to consider as indicators for a double invoice entry. You can choose from: Reference, Company code, Document date.
Here is part 2 of the answer to the previous question: YES, Logistics Invoice Verification can be set up in a way that invioces are checked cross-company code. If you do NOT mark the field company code, than this field is not checked, and the same invoice cannot be entered for 2 different company codes.
First, the system tries to find a BSIP record with the same values in the fields below:
- Vendor number
- Document currency
- Amount in document currency (this only if Reference is NOT ticked in table T169P)
- Company code (only if ticked in T169P)
- Document date (only if ticked in T169P)
- Reference (only if ticked in T169P)
If there was a BSIP entry found, message M8 108 will appear as a warning. Again, you can change the msg type to error if you like (user-specific).
Also, Logistics Invocie Verification can be a 2-step procedure: first, the invoice creation (entry in table RBKP) and second, the posting of this invoice to Accounting (entry in table BKPF). In most cases, this happens in the very same moment when you press Save in MIRO, but it could be also set up in your company that you do these 2 steps separately.
That's why after the posted invoices (BSIP) were checked, the system tries to check the invoices not yet posted to Accounting (invoice document status is "Not yet posted"). This is to make sure an entered but not yet posted invoice is also checked early enough. Basically the same fields as above are checked, but the message is a different one: M8 642. Default type is warning, changeable to Error if you like.
Hope that helps, points welcome
Csaba

Miro: Green signal ( posted/ can not be posted)

Hi expert
Before putting final amount for miro, system as per system show( RED Signal) balance not sero.
But in my caseBefore putting final amount for miro, system as per system show( Green Signal) posted/ can not be posted.
Regard
Nabil

Hi,
Check all setting for MIRO
1. Maintain Company Code in Table T169P
2.Maintain the tolerance limits for the Company code in t.code:OMR6 (for tolerance key PP,DQ & DW)
3.Maintain setting of messages for ERROR in t.code:OMRM ( M8-81 & M8-87)
4.Maintain Default Values for Tax Code in t.code:OMR2
5.Just check document type RE in OBA7 t.code
Regards,
Biju K

MIGO-GR message

Hello experts:
When i use MIGO-GR to do goods receipt from PO there is an message
"Table T169P:entry 1000 does not exist"
1000 is my company code, what should i do to define or set this from SPRO to solve this issue?
Thanks

hi
for such table entry errors u can follow following process
goto SM30 give table name T169P and click on custmising, system will show u all possible customising for that table
now select one from the area ur working (in ur case PURCHASING)
now maintain missing entries and done
regards
kunal

Table T169P

Similar Messages

Maybe you are looking for