OLD ERP Vendor stock rejection through SAP

Material stock is lying at vendor .The PO was of old ERP system.Now, this stock is to be returned back to Vendor due to rejection through SAP. How?

Hi Mukund,
Since, you have not posted the Migo in sap and the material want to send back to supplier. In this case return delivery is not possible. Kindly make return purchase order (tick return item in me21n) and then post migo. migo will be done thru movement type 161 and stock will be deducted from your store location. Subsequently you can post j1is and credit memo.
I think, it will help you.
If helped, kindly reward.
Ishu

Similar Messages

Material rejected through quality inspection lot goes to blocked stock

Dear All,
All materials that are rejected through quality inspection lot should go to blocked stock. My client want to generate a report for viewing what all materials are rejected. How can do that?
scenario2: If the materials are rejected then can they be automatically be sent back to the vendor (return to vendor). if possible
pl send me some suggestions...!!!
pl discuss

Hi,
See mvt of material directly to blocked stock u can do by setting the Selected Set of ur specific UD code. in QS51/QS52. there is one column near to code, set R=rejected and set that field "BloCked Stock" . Define there and execute ur transcation, whenever u provide an UD system automatically post the stock in blocked location.
MCVX is the report where u can get the stock lying in blocked location, or for temp. purpose use QVI and developed the new report.
regards

SCADA - XMII - ERP integrations through SAP PI

Hi Experts,
I have an integration scenario comprising of a SCADA system & SAP ECC. Could anybody suggest some document / send reference links on SCADA - XMII - ERP integrations through SAP PI.
Useful response would be appreciated.
Regards,
Santhosh

SCADA-XMII integration
Scada system should always remain connected to some Historian system. You can directly connect to SCADA system to xMII using vendor specific UDS (Universal Data Servers) Like Citect UDS ...
If vendor specific UDS is not available in MII then you can make it possible if the SCADA system is OPC complaint, through OPC UDS DA, but it provides only current data without any mata data information.
As a robust business practice it is not recommended to use direct SCADA connectivity to xMII, it should go through some Historian( Citect, Wonderware, Siemens...many more) so XMII will be able to get all plant floor operations data in history & current modes.
XMII-ERP Integration
XMII supports IDOC & BAPI communication with ERP system using various SAP connectors available in XMII as in SAP BC, SAP JCO.
Specific to PI Sheet, you can download various control receipe, process orders data using IDocs.
BAPIs can be used to do "process order confirmations" back to ERP system and make changes in process data.
Let me know if you would like to know about specific SCADA system- xMII connectivity or specific activity in PI.
Thanks
Ram Upadhyay

Payment Advice needs to be send as mail to Vendor through SAP.

Hi,
There is a requirement in my businees related to payment advice mail. After running T-Code: F110, spool getting generated with all the payment advice (lets say 20 advice at a time for different vendor). now we want to mail each advice to respective mail through SAP itself. Could you please provide me some idea through which i can achieve this functionality.
Thank you,
Manya.

Please search SDN, you will find all the information already existing on this feature, e.g.:-
[F110 payment advice by e-mail;
Basically BTE event 2040 and 2050 is used for it.
Regards,
Gaurav

Error while making vendor rejection through 122 mvt

Dear Friends,
User made GR for a Subcontract Material against a Scheduling Agreement. Then part qty he wanted to reject through 122 mvt. System gives the following error.
Purchase order 8101000081 00210 has no component 000ADC120000 in plant 1000
Message no. M7387
Kindly give some solution for the same. Both header and Component materials are available in the plant.
Regards,
Ask

Hi,
Kindly check movement type groups in SPRO>Logistic genaral > Tax on goods movement > indai > Business transactions > Subcontracting > maintain movement tye groups
0001     122     O
0001     541     O
0001     544     O
0002     101
0002     105
0002     542     O
0002     543     O

ECC TO SRM-MDM CATALOG THROUGH SAP PI

We have a scenario where we are sending data from ECC to SRM-MDM Catalog through SAP PI and data is coming from ECC through proxy and sending to SRM u2013MDM catlog through file adapter. In ESR part we have used SAP defined standard service interfaces (CatalogueUpdateNotification as sender interface and MDMInfoRecordDataTransmission as a receiver interface). The mapping used is also standard one.
Now we have got requirement to send the data for vendor mat no, manufacturer field of info records from ECC to SRM-MDM catlog. But we are unable to find out these two fields in standard interfaces/messages. Can anybody guide us how to add these fields in the current data types or is there any other standard interfaces we can use.
Thanks in advance.

Hi Shiv,
Many thanks for your reply.
Since we're not using XI / PI scenario and this is an upgrade from SRM 5.5 to SRM 7, Iu2019m using the same approach that was already used in SRM 5.5 with CCM 2.0.
The idea is that the catalogue and all the records maintained need to be associated to a contract. So, I add the contract ID and the correspondent contract item in the import file, in addition to the supplier name, product ID, price information and so on. I mapped the contract ID with the field contract price.
In relation to the price information fields, as I want it to be visible for any user that accesses the product catalogue, I tried different approaches:
1.Using OCI Price information u2013 amount, currency, price base quantity and price base quantity UoM;
2.Using OCI Price contract u2013 amount, currency, price base quantity and price base quantity UoM;
The first approach didnu2019t work very well, as I was not able to see price information when accessing the catalogue. I could only see it once I transfer the items to the SC. In addition, this approach had one problem. The products were displayed but it was not possible to select the items one by one. To do that I needed to select all the items of the catalogue and after that the detail of the contract ID was displayed in every item, allowing me to choose the items that I want to select to my SC.
The second approach was better as the information was visible when accessing the SC and I was able to select all the items, one by one, as it should be. The main problem of this approach was that Iu2019m getting errors in the SC when the materials have stock u2013 u201CInterface data contains errorsu201D. Or alternatively, if the items didnu2019t have stock, the SC was possible, but when I tried to create a PO from that SC, It simply does not work.
So, can someone help me? Any ideas?
Thanks in advance.
Best regards,
Andreia

Re : Inter company stock transfer through EDI

Hi
      How to do the intercompany stock transfer through EDI. In this if Purchase order is created from one comapny a sales order should created automaticall in another Company. Fot this what is the SPRO settings.
How to do this.
Thanks
Anto

Hi,
continues from here,
Inbound file:     edi_in
Function module:     See text below.
Status file parameters
Directory:     /home/edi/<portname>/
Outbound file:     status.idoc
Function module:     Leave blank if using above
u2022     Both the portname and the exchange directory should be created according to the same naming convention. However, the portname should be in upper case whereas the corresponding directory name should be in lower case (see examples below).
     Portname (upper case):
                         <portname>
     Exchange directory name (lower case):
                         /home/edi/<portname>
     where <portname> consists of:
     EDI<system name><client number><id char>
     <system name> is the name of system on which port exists eg.      F01, PG1 etc.;
     <client number> is name of client on system which will use this      port; and
     <id char> is a single alphabetical character such as u2018au2019,u2019bu2019 etc.      typically,      u2018au2019 will denote dynamic outbound file naming (used      for testing) whereas      u2018bu2019 will denote static outbound file naming.      All ports will use static      inbound filenames.
For example, the name of a port using dynamic file naming on system F01, client 610 would be named EDIF01610A. The exchange directory would be named edif01610a. Similarly, the name of port using static file naming on system PG1, client 600 would be EDIPG1600B. The exchange directory name would be edipg1600b.
Note that the function u201CEDI_PATH_CREATE_USERNAME_DT_TMu201D can be used in the u201CFunction moduleu201D field of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.
2.4.2.     Control of EDI processes in R/3
2.4.2.1.      Maintain: Outbound Process Code (WE41)
IMGCross-Application ComponentsALE Extensions  Outbound
Check that the outbound EDI processes in the R/3 system are defined. Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.
The following assignments are available for R/3:
2.4.2.2.      Maintain: Inbound Process Code (WE42)
IMGCross-Application Components  ALE  Extensions  Inbound
Check that the inbound EDI processes in the R/3 system are defined. Indicates what kind of inbound processing to execute.
     A long list of options is available under Processing by function module, relevant ones are:
INVF     INVOIC FI     Invoice receipt (Financial Accounting)
INVM     INVOIC MM     Invoice verification (Mat Management)
ORDC     ORDCHG     Change customer order
ORDE     ORDERS     Create customer order
ORDR     ORDRSP     Purchase order confirmation
2.4.2.3.      Control: System Process Codes (WE40)
     Choose Processing by task. Check that the codes indicating the type of EDI processing error are defined. The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.
2.4.2.4.      Control: Status maintenance (WE47)
     Check that the codes indicating status of IDoc processing are defined. The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50. These values are delivered by SAP and cannot be customised.
2.4.2.5.      Control: Partner Types (WE44)
     Check that the codes that identify the commercial relationships between the receiver and sender are defined. Values are delivered by SAP. Names of the programs and routines that validates the entry of the EDI trading partner ID:
Partner type     Report name     Form routine
B - Bank     RFETESTP     READ_T012
KU - customer     RSETESTP     READ_KNA1
LI - vendors     RSETESTP     READ_LFA1
LS - logical system ( ALE)     RSETESTP     LOGSYS
2.4.2.6.      Control: Forward Inbound (WE45)
Allows for the forwarding of IDocs to a specific application. Contains the exactly defined destination of an inbound IDoc within the SAP system. Usually no changes are required.
2.4.2.7.      Control: Status Process code (WE56)
Choose Processing by task: The following set-up has been provided as default:
Process code:     EDIS
Identification:     TS30000078
Description:     EDI-IDoc status record processing
The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.
3.     MM IMG CONFIGURATION
3.1.     Global settings (IMG):
3.1.1.     Units of measure (IMG  Global settings):
The ISO code is important for EDI. It is used to convert the internal SAP units of measure into standard units.
The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).
3.2.     Link Schema to Purchase order
Check the following:
IMG  MM  Purchasing  Message determination  Message determination  Message Schemas
Execute transaction u201CDefine Message Schemas for Purchase Orderu201D
Select transaction: Assign Schema to purchase order
Add:      Usage =B for output
     Application = EF for purchase order
     Procedure = RMBEF1 for purchase order
3.3.     Link application to EDI interface via message control:
IMG  MM  Purchasing  Messages  Output Control
Check following under Output Control:
     Condition table
     Access sequence
     Message types
     Message schema
     Output control
3.4.     Enabling Multiple Output for Purchase Orders (Optional)
For example: EDI & Printing
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022     Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)
u2022     Goto Define message types  maintain message types:
     Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)
u2022     Goto Message Schema  define message schema  maintain output determination procedure:
     Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)
u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
     - Add a NEU1 record to table TNAPR. The program FORM Routine and layout must be specified. (Copy an existing NEU record). (Transaction OMTB)
u2022     Goto Processing program  Define Processing program  Output by partner type.
     - Add NEU1 record for VN (vendor). (Transaction OMTG)
3.5.     Link Output type (fax=2, E-mail=7) to NEU (Purchasing)
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
     - Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)
u2022     Goto Processing program  Define Processing program  Output by partner type.
     - Add NEU record for VN (vendor). (Transaction OMTG)
4.     SD APPLICATION REQUIREMENTS
Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.
Reference SAP Course manual Chapter 11.
4.1.     EDI Configurations
4.1.1.     Conversion of SAP item categories to IDOC item categories (VOE1)
IMG  S&D  EDI  EDI Messages  Conversion of SAP item categories to IDOC item categories
Add the following entry:
For Standard Item description :     0     OR     LDN
Typically error message: ''Transaction LDN is not defined".
4.1.2.     Partner functions
IMG  S&D  EDI  EDI Messages  Configure EDI Partners Partner  Application  Partner function
Check that the following partner functions exist: (at least)
SP     Sold-to party
VN     Vendor
BP     Bill-to party
SH     Ship-to party
Note - the German abbreviation is passed to the IDoc.
4.2.     S&D Sales Configurations
4.2.1.     Maintain Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Define item categories
Add LDN for standard item:
          Item type = B
          Relev for billing = B
          Tick following:     Bus data item
                              Sched line allowed
                              Credit active
                              Pricing
          Screen seq. grp = N
4.2.2.     Assign Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Assign item categories
Add/Update the following entries:
     1     2     3
Sales doc type     OR     OR     OR
Item category group     NORM     DIEN     LEIS
Item category     LDN     TAD
LDN     LDN
4.2.3.     Assign Schedule line categories
IMG  S&D  Sales  Sales document  Schedule lines  Assign Schedule line categories
Add Item category LDN to table (with no other parameters).
4.3.     S&D Pricing Configurations
4.3.1.     EDI pricing condition types
IMG  S&D  Basic functions  Pricing  Pricing control  Define condition types  Maintain condition types
Maintain the following condition types:
     EDI 1 - Calculate type =C for Quantity
     EDI 2 - Calculate type = B for Fixed amount
4.3.2.     SD Pricing procedures (V/08)
IMG  S&D  Basic functions  Pricing  Pricing control  Define & Assign pricing procedures
Maintain pricing procedure for ZVAA01 (Standard).
Select control and add EDI1 and EDI2 as steps 1 and 5 respectively with no other parameters.
5.     INVOICE IMG CONFIGURATION
No additional IMG configuration (not partner specific) was needed for Inbound Invoice processing.
Thanks,
Swamy H P

Follow up material - old material's stock goes down and up

Hello,
I have a question related to Follow up material. Lets assume that material A is to be replaced by material B, this is specified in the MRP4 view. In the field Eff.-Out an estimate of when the last unit of material A will be received is given in.
If material A's stock drops down to 0 then material B should kick in, but what happends if afterwards material A's stock goes up again and then both material A and B are in stock. Will SAP notice material A's stock level and use it?
Please advice! Thanks!
mr

I have a question related to Follow up material. Lets assume that material A is to be replaced by material B, this is specified in the MRP4 view. In the field Eff.-Out an estimate of when the last unit of material A will be received is given in.
If material A's stock drops down to 0 then material B should kick in, but what happends if afterwards material A's stock goes up again and then both material A and B are in stock. Will SAP notice material A's stock level and use it? \
If you don't know the "Effective-Out Date" (MARC-AUSDT) [because your stock situation is always changing), don't define it in material master. System will try to ramp down the stock of old material first and use the new one after that.
However, you should take measures to prevent increasing the stock from the old material. In the system you can block it for purchasing as it was told you already.
Regards,
Csaba

Error Crystal report When viewed through SAP B1

Dear Experts
SAP B1 8.8 PL 16,SQL 2008
I am facing error (Unable to retrive data from database)(Vendor code-156) while accessing Crystal report from client machine throgh SAP B1.I have imported Crystal report through manage layout.The crystal reported is in shared in SAP server B1 SHR folder.I am able to access data from crystal report when viewed otherwise.When accessed crsytal report through SAP b1 on SAP Server crystal report is working fine.
Thanks & Regrds
Saurabh Lamba

Hi Saurabh Lamba,
Go To Administration / System Initialisation / Authorisation / General Authorisation & Set Authorisation for user.
If you have to Set Authorisation for user allready then follow this steps.
1.Restore Database as Test Company.
2.Export Report From Live Company.
3.Import this Report in Test Company as different name.
4.Export Report from Test Company have you Imported as deifferent name.
5.Again Import this Report in Live company as different name
I don't know what's the logic behind it.
Thanks,
Srujal Patel

POS DM: Stock updates in SAP Retail

Hi!
We are implementing SAP Retail (ERP 6.0 EHP4 stack 3), SAP PI (Netweaver PI 7.1 SP 8) and SAP BW (NetWeaver 7.0 ehp1 stack 4, incl BI content 704, SP 3 ) for a client. Their POS system is a 3rd party system, i.e. not SAP POS, and it does not contain any stock information.
This issue concerns stock updates in SAP Retail using POS DM:
On the busiest day of year, my client has 347 000 POS transactions in total from all stores, and in one year they have 30 mill POS transactions. My client requires that SAP will provide them with near-realtime information on stock availability, as this is an important way of providing good customer service. The stock information should be available in SAP Enterprise Portal and SAP Retail Store, as well as standard SAP gui transaction. In addition, the webshop (external system) should have as accurate information about stock as possible, at least it should be updated once every 30 minutes.
My client also has a requirement to be able to create purchase orders during office hours (store opening hours), based on MRP runs. This means they must have as accurate stock levels as possible for running MRP. Stock levels are also used in ATP checks, when deciding whether to pick customer orders from store inventory/stock or to create purchase requisitions.
All these requirements have led us to believe that the best way to solve this, is alternative A:
- to update stock continuously during office hours, using WPUBON to create material documents, one for each POS transaction. Sales and tenders will be updated in SAP Retail using WPUUMS and WPUTAB.
Some challenges this will create:
a)     It will create 347 000 WPUBONs on the busiest day of year, all within 10-12 open hours.
b)     If we have same amount of material docs and FI docs, they will use 30% of the available 8 digits within their number ranges per year.
c)     The idocs will fail if there are article locks simultaneously. (However, this can be handled by updating products only at night time (using batch jobs) and using batch job to handle failed idocs)
Edited by: Øystein Emhjellen on Jan 4, 2010 2:15 PM

Alternative B:
- we have considered to use WPUUMS and WPUTAB, updating stock levels only once a day. The solution we then must use for taking into account actual sales data is described in SAP Note 1088886 - Using the interface for online stock queries. If we choose this, we need to check during the day for each article any sales, to reduce stock in reporting/screens, ATP checks and in MRP runs. We must also create a program to check for articles sold before sending stock data to webshop (external system). (As we do not know which articles have been sold, we must create our own version of RFC - /POSDW/SALES_QUERY_RFC, to enable that the article number does not have to be specified. Rather, the article numbers (and sold quantities) have to be returned to ERP based on what was actually sold.)
We consider this alternative more risky, due to the need for changing behaviour of standard programs for MRP and ATP check. It will also create a number of RFC calls between SAP ECC and SAP BW.
My questions on this issue are:
i)     Will alternative A be preferrable, if hardware requirements are handled?
ii)     Do you see any additional challenges related to alternative A?
iii)     Will alternative B be adviceable, concerning the program changes/enhancements involved?
iv)     Are there standard implementations of SAP ECC, that includes the use of RFC - /POSDW/SALES_QUERY_RFC. I.e. standard programs in SAP ECC that uses the information from this RFC call?
Thanks for any advice !
Best regards,
Oeystein Emhjellen

Vendor payment advice through email

Hi gurus
i want to send vendor payment advice through email , i am using the form F110_IN_AVIS for payment advice
and from the report RFFOAT_P i want to send the email , is any configuration needed to send the email , or just i have to give selection detials properly and it will work ,
regards
m.a

Hi Afzal,
For sending Payment advice by E-Mail, "You need to copy SAMPLE_PROCESS_00002040 and adjust it to write code as per your requirement. This BTE runs for each payment advice note to be sent and in the module, it is mentioned 1=print, 2 = Fax and I=mail, so you can set your priority, that if an E-Mail address is maintained in the vendor master, send mail or if no E-mail address is maintained send Fax, and if both are not possible shoot a Print.
From Configuration side, you need to maintain the Z copy of SAMPLE_PROCESS_00002040 in FIBF transaction under the Process module of a customer without country or application indicator.
SAP Note 836169 - Consulting: Payment advice notes by email or fax.
Regards,
SAPFICO

Vendor wise Rejected Purchase Material List

Dear Sir,
Kindly guide us , as which Tcode or Report is available to see the Vendor wise Rejected Material deatils for the Purchases .
Full marks are assured for the suggested solution
Regards
B Mittal

how do you reject?
Do you just mean POs with return items?
Or a usage decision to an inspection lot in QM that posts the stock to blocked stock.
or just a return material movement 122 or 161 or even a cancelled Goods receipt (movement 102)
You can list POs with return items with ME80FN by using dynamic selections that select based on return indicator.
Lists are available in QM menu > Quality inspection > Info system.......
Movements can be listed with MB51.

How to clear Vendor Debit item Through F110

Hi All,
I have a new requirement,
I have a vendor for which transactions are posted in multiple currecies, like USD & EUR.
I have 2 invoices for this vendor, one is in EUR, and other one is in USD, along with this i have a dabit balance for this vendor which generated through a credit note.
now when iam trying to make the payament for this Vendor thrugh F110, and try to clear the debit amount also, the system is throwing one error message saying that "Enter incoming payment method for the debit amount "(whici is in USD)
Please let me know how to solve this issue
Thanks in advance

Hi Robert,
This is the content of SAP Note 164835 as follows:
SAP Note 164835 - F110: Clearing credit memos and
invoices
Note Language: English Version: 14 Validity: Valid Since 29.05.2008
Summary
Symptom
When you execute a payment run, you select credit memos and invoices for a
customer or a vendor, but the system does not clear them together. In the
payment (default) log, the system may generate the error message FZ
347:"...none of the payment methods defined can be used for these items".
Other terms
F110, SAPF110S, clearing, FZ 347
Reason and Prerequisites
The items to be cleared do not match in particular fields (see below).
Therefore, they are not paid together.
You can set a payment method only for either outgoing or incoming payments.
This explains the error message FZ 347.
Example
- Payment run is executed with payment method U for outgoing
payment.
- Credit memo is not cleared against invoice.
- Invoice is paid with U.
- Error message FZ 347 is generated for the credit memo.
Solution
The following explains in general how to clear, and describes some options
for eliminating errors. The logic of the grouping in the payment program is
independent of the type of the documents (for example, invoice, credit
memo, down payment, cross-company code posting).
General information
o You can pay open items together using the automatic payment
transactions, but only if certain fields are identical. The
structure ZHLG1 specifies these fields. Important fields are:
- Currency
- Receiver
- Payment method in the item
- Bank details in the item
o Whenever invoices and credit memos are in different payment groups,
you cannot clear them together, even if the credit memo contains an
invoice reference. If you set a payment group for a business
27.12.2010 Page 2 of 4
SAP Note 164835 - F110: Clearing credit memos and
invoices
partner (grouping key in the master record), then this is saved in
structure ZHLG1 (field PAYGR). This way the invoice reference in
the credit memo is overridden if they do not belong to the same
payment group.
o Invoice and credit memo must be due at the date of clearing. The
due date of a credit memo without invoice reference (BSEG-REBZG) is
the baseline date for payment (BSEG-ZFBDT), and for a credit memo
with a fixed value date (BSEG-REBZG = 'V'), the due date is
calculated in the same way as for an invoice. For credit memos with
invoice reference, the due date of the invoice applies.
o You cannot clear credit memos and invoices if the payment is
supposed to be made using a payment method set for the POR
procedure.
Invoices are grouped with a POR number with the document number as
an additional part of the grouping key so as to save the individual
payment required for POR payment methods. Invoice-related credit
memos for invoices with POR numbers receive the same grouping key
as the related invoice. This ensures that the clearing is
performed. However, you can no longer make payments using the POR
payment method because this payment method allows only one item to
be paid. However, you can make the payment using a different
payment method.
The POR procedure is only relevant for payment transactions with
the Swiss Postal Service. Consequently, the relevant fields in the
document and in the business partner master record are only of
importance in Switzerland.
What can you do?
o Check the payment methods in the line items (field BSEG-ZLSCH). For
clearing, these must be filled with the same value.
o If you have entered a specific payment method for the items, then
check Customizing for this payment method (transaction FBZP). The
indicator "Single payment for marked item" should not be set there.
o Check the field "Grouping key" in the master record of the business
partner for payment transactions in the company code. If, for
example, there is a grouping set according to assignment number,
then the invoice and credit memo must have the same assignment
number in the business partner line for clearing. Using transaction
OBAP, you can define which fields of the key you want the system to
use for grouping.
o Check the indicator "Pay all items separately" (LFB1- or
KNB1-XPORE) in the master record of the business partner for
payment transactions in the company code. If this field is set,
each open item for this business partner is paid separately.
o If you have set the indicator "Separate payment for each Business
Area" (T042-XGBTR) for the payment program (all company codes) in
Customizing, check the business area in the items. They must match
in this case.
o Check the house bank in the line items (field BSEG-HBKID). The
27.12.2010 Page 3 of 4
SAP Note 164835 - F110: Clearing credit memos and
invoices
values must also match for clearing. A document without house bank
can only be cleared with a document with house bank if this house
bank is defined in the master record of the business partner
(LFB1-HBKID or KNB1-HBKID).
Make sure that the house bank from the payment program is filled
for any reset clearing documents (see Note 159607).
o Check the partner bank type in the line items (> Other data > field
BSEG-BVTYP). These values must also match for clearing. You can
specify the partner bank type in the master record of the business
partner for general payment transactions.
o For postings to one-time accounts, the address data is encoded and
saved in field BSEC-EMPFG. The coding routine has been changed in
Release 3.0E. Therefore, if you want to offset documents from an
earlier release against documents from a later release (for
example, after an upgrade) you need to check the contents of this
field. These values must match for clearing. If this is not the
case, the documents from the earlier release need to be reversed
and be posted again. If reversal is not possible, contact SAP
Support.
o If you do not clear using a payment method set with POR procedure
(with or without invoice reference in the credit memo), then check
the contents of the fields BSEG-ESRNR, BSEG-ESRRE and BSEG-ESRPZ.
They must not be filled if you do not enter a payment method in the
item.
o If you set a separate payment for each payment reference (for
example separated by a CID number in Norway or reference number in
Finland) (FBZP > Paying Company Codes > field T042B-XKIDS), then
the items for a clearing in field BSEG-KIDNO must be the same. Note
that the Customizing setting (T042B-XKIDS) is effective only if
vendors are involved in the payments. When you separate the
payments by payment reference, also take into account that no
outgoing payment can be generated for a payment reference for which
only credit memos exist.
o Check the structure ZHLG1 in your system. If you have inserted
additional fields there, the line items must also match in these
fields. Contact your consultant.
Header Data
Release Status: Released for Customer
Released on: 30.05.2008 10:55:56
Master Language: German
Priority: Recommendations/additional info
Category: Consulting
Primary Component: FI-AP-AP-B Payment Progam / Payment transfer
(DE, JP, US)
Secondary Components:
27.12.2010 Page 4 of 4
SAP Note 164835 - F110: Clearing credit memos and
invoices
RE-RT Rental
The Note is release-independent
Related Notes
Number Short Text
1084325 FSCM-BD: Payment method for invoice-related credit memo II
305414 F110: Unintelligible grouping of documents
197626 Partner bank category in RAs and payment program
159607 F110: Reset clearing is not offset against
143311 F110:Incorr.due date for cred.memo w/ fix.val.date
109233 F110: message FZ347 or several payment documents
86578 Guidelines for F110 Payment Program (W/Check mgmt)
33288 Payment methods for rental agreement
22856 Customer credit memos are not paid
20484 Payment program does not clear due items
4904 Credit memo clearing or down pmnt clearing for POR

Vendor Return Delivery through Quality Notification.

Hi Experts,
I m doing vendor return delivery through quality notification with action box , after giving PO NO. & Material document no we are getting the following error
1) Could not create return delivery
2) Deficit of PU IR quantity 2.000 EA
For the GR based IV reversal after IR tick is not active.
Kindly suggest possible reason for the same
Thanks & Regards
Rajesh

Hi
There is deficit of Quantity i.e the quantity lying in stock is less than 2. and secondly for GR based invoice verification the IR tick should be there in PO in Invoice tab.

Configuring double invoice check for vendor invoices posted through FB60

Dear all
Can anyone tell me how to configure double invoice check for vendor invoices posted through FB60.
for miro documents..we can use Tcode OMRDC
Is there any such tcode which can be used for configuring fi invoices for double checking..
regards
Expertia

Dear Expertia,
In FI,when checking for duplicated invoices, the system compares the
following :Vendor, currency, company code, gross amount of the invoice,
reference document number and Invoice document date.
SAP Note 305201 clarifies this in a more details; please read it.
The following fields must be identical for Duplicate invoice check
     Company code                              (BUKRS)
     Vendor number                             (LIFNR)
     Currency                                  (WAERS)
     Reference number                          (XBLNR)
     Amount in document currency               (WRBTR)
     Document date                             (BLDAT)
If the document is having any one of the above filed different then the
system does not consider it as a duplicate invoice.
Also It will check duplicate invoice check in vendor master data and
in posting key is there check box selected for sales related
The setting you making in OMRDC i.e Materials management->Logistics
Invoice Verification->Incoming Invoice ->Set Check for Duplicate
Invoices is only valid for MM and not FI invoices posted via FB60/FB65
You should check the F1 help on field "Chk double inv." (LFB1-REPRF)
in the relevant vendor master record (transaction FK03).
Please also check, that message F5 117 has been set correctly in the
IMG using this path:
Financial Accounting -> Financial Accounting Global Settings ->
Document -> Default Values for Document Processing -> Change Message
Control for Document Control For Document Processing
Finally & mainly, go to the relevant posting key is defined as sales
related in transaction OB41. You have to flag this field if the
duplicate invoice check should work.
I hope this helps You.
mauri

OLD ERP Vendor stock rejection through SAP

Similar Messages

Maybe you are looking for