Outline agreement - invoicing party at header

All,
I have couple of outline agreemnts which are contracts actually.
At header level, invoive party field is coming grayed out for some contracts and some other its editable.
I think for central Pur Org it's grayed out, not sure.
Any one any idea why this field is grayed out.
Please advice.
Thanks,

call offs means release orders , right?
I have both released and non released contracts which have Invoice party field non editable.
Released means released to PO.
Please advice.
Thanks

Similar Messages

Invoiceing party at header level in MIRO

Hi,
We have different invoicing parties defined for the same vendor at the plant level in Alternative Data. But, the invoicing party in MIRO is at the header level. When we do MIRO by vendor, it does pull in all the POs but those POs have different IPs because they are from different plants. However, in MIRO, the system deposits the IP from the first PO at the header level and will create the A/P for all the POs against that IP.
Any way around this? To make the system determine the IP from the underlying PO and do the MIRP-A/P accordingly i.e. post the A/P to the correct IP defined in the PO? Of course, we could do MIRO by plant but considering the very high volumes and the number of plants we have, that is rather inefficient and we would prefer doing it by the vendor code if possible.
Thanks.

Dear Tengku
Please try with this.
Go to V/08, for the net value field, maintain Routine 16 in the Alt. Cal. Type. Also add Routine 17 to Netvalue.
As you know Condition types are assigned at each item level. So rounding off is calculated at each item level. But by assigning a tick in the Group Condition while defining Rounding off Condition, you can do rounding off at invoice level. The difference is automatically adjusted at each item.
thanks
G. Lakshmipathi

MIRO - Invoice Party - User Exit needed

Hi,
I have a requirement like this....
On MIRO tcode, the i need to put a condition if the user gives a Inv Party (3rd tab 'Details' on Header data of MIRO screen) other than the defalut one (vendor which comes by default with the PO)
<u>Inputs to MIRO are :</u>
1. invoice date on first tab of header data
2. Existign PO number in Purchase Order/Scheduling Agreement ( just below the header data block
3. in 3rd tab of header details (Details tab), on Inv.Party field, it takes the vendor number by default when we give the 2nd input (PO number)
Can any body tell, which function module exit to work with ?
PLEASE DO NOT GIVE ME the list of exits and badis by executing the ZUSEREXIT program.
I have already done this.
I would like to know which user exit to select out of this total exits.
Thanks for your Help
"Share and Learn"

Hi Ali,
My requirement is like,
the user should not be allowed to give the Invoice Party field - value as different from the one different from the vendor number which already assigned to the PO while PO Creation.
Please read the query in this thread for more details.
I have found the list of exits, for MIRO, by executing ZUSEREXIT, and i got a list of exits and one BADI. But I am not sure which Exit will work for my requirements.
========== xxx ============
Please, also tell me, how to identify the exact 'function module exit' which suits to our requirement, from the set of all exits displayed after executing ZUSEREXIT program. (approaches/methods , u follow to identify)
Thanks

Difference B/w Framework & Outline Agreement

Hi Gurus
I am new to SAP MM, can anyone please tell me the difference b/w framework orders and outline orders/ agreement.
General examples of this regard will be very helpful.
Regards
Imran

Dear,
A Frame work order is :
Purchasing document used for the procurement of materials or external services. Instead of stipulating a specific delivery date, this type of purchase order has an extended validity period. Goods or services can be supplied or performed against it over this period without the need for any further written instruction to be issued by the buying entity.
Framework orders are defined with document type FO. They are used in accelerated procurement processes in connection with preventive maintenance (servicing) plans or invoicing plans, and for blanket purchase orders (purchase orders with specified limits).
A framework order covers multiple procurement transactions over a longer period in cases where the administrative costs of processing discrete POs would be disproportionately high.
An Outline agreement is :
Outline agreement also referred as Contract in SAP.
Outline Agreement can be of 2 types:- Contract and SA.
Contract is where you have a contract with the vendor,may be a for a predetermined quantity or predefined value. So everytime you need the material, you need to make PO ref the contract asking for the delivery of the material. In such instance when PO is ref with contract its called contract release orders or call off orders.
Scheduling agreement is a long term purchase agreement, where you will keep issuing the delivery schedules whenever there is a change in requirement or at predetermined time intervals. The delivery schedule can be on hour/daily/weekly/monthly basis. But it will contain different zones viz. firm/tradeoff/Forecast. Firm zone schedules are confirmed requirement and need to be taken by ordered party. Tradeoff zone requirement is to purchase the raw materails and ordering party is liable to pay raw material cost, in case of requirement cancellation. Forecast zone requirement is to help the vendor to plan his requirements.
SA is also an agreement with the vendor for the supply of matl, may be a quanity or value. The delivery dates will be maintained in ME38 ref the SA which are called delivery schedules.So you can maintain the delivery schedule and communicate the vendor on Forecase basis or JIT basis. And when you need some more matl then will only create SA deliveries using ME38. SA could be of 2 types:- without release documentation-system will transmit the delivery info to the vendor once you save the document.
With release documentation- after creating the delivery schedules you need to create SA release using ME84.
The main difference between contract and SA is volume of docs generated would be higher in contract since everytime you need to make a PO ref the contract and its time consuming, whereas SA can be integrated with MRP such that it automatically creates delivery schedules during MRP run provided if there is a requirement to the matl.
Regards,
Syed Hussain.

Global Outline Agreement Distribution

Hello,
i try to distribute global outline agreement ( transaction type GCTR ) from SRM 4.0 to ERP 2004.
But I can´t find in my browser ( its service = bbp_ctr_main ) the header data "Distribution".
I see in my header data only following taps:
Basic Data / Documtents / Conditions / Output Logs / Status / Approval Preview
I set up following things till now:
- IDoc type = BLAREL02 as Inbound Processing in SRM System
- IDoc type = BLAREL02 as Outbound Processing in Backend System
- transaction type = GCTR with internale number range in SRM System
- transaction type = GCTR with external number range in Backend System
- BADI: BBP_CTR_BE_CREATE in Method: CONTRACT_PROCESS_TYPE_FILL
   EV_PROCESS_TYPE = 'GCTR'.
- BADI: BBP_DETERMINE_LOGSYS in Method: CONTRACT_LOGSYS_DETERMINE
   CV_LOGSYS = 'our Backend System'.
- PPOMA_BBP - Attributes; Tab: Function -under Local I mapped the Purchasing Organisation and the
   Purchasing Group with Backend System
*Which customizing is still missed to see this tab "Distribution" in the header data?!
Would be glad if someone could help.
Best Regards
J.F.

If you really want to do GOA, you've got the wrong service (CTR_MAINCC is the one you are looking for). The role stratpurchaser* has both transactions: contract and global outline.
BBP_DETERMINE_LOGSYS does not need to be implemented, BBP_CTR_CREATE_BE neither (maybe for condition mapping!).
You are missing blaord for replication to ECC from SRM, you are missing BBP_SRV if you want to make GOA for services.
Along the way you will probably find that some other things need to be customised in ECC (setting up of global company, some other minor stuff like company code that's missing in ECC).
So basically you don't miss any customising for seeing the tab, but for replicating GOA you DO miss something.
In the Wiki section for SRM on this site you can find the configuration guide for setting up of contracts and GOAs, if you follow that you will have done around 90-95% of all necessary steps.
Regards,
Robin

ECC Report showing Outline Agreements WITH related Release Orders

Does anyone know of a report in ECC which will display all Outline Agreements together with all the Related Release Orders associated with each Agreement Number?
I have trawled through hundreds of SAP transaction codes and cannot find something that will give this information - I can use ME3N of course, but ideally my Users want to be able to search on ALL Outline Agreements and see the associated release orders
If anyone is able to help it would save me a headache!
Many thanks
Jane

You can get Goods Movement from MSEG Tables. Why do you need Goods Movement in Sales Flow?
While Creating Every Document in SAP R/3, we will put reference Document and Item.
While Creating Sales Document, Customer PO is reference Document.
For Delivery, we can create againest Sales Document or Invoice etc.
For Invoice, either Delivery or Sales Document.
Pull all the Data Sales, Delivery, Billing and Shipping with Reference Documents into ODS.
You need to create a Infoset on these ODS.
Let me know if you still have any Questions.
Nagesh Ganisetti.
Assign points if it helps.

2 'Invoicing party" in Vendor details (MK02)

The zone 'Invoicing party" becomes empty and non-modifyable in ME31K after having added another 'Invoicing party" in the Partner Functions of the vendor in MK02 (requirement).
After this change in the Vendor details, the aim is to have the zone "Invoicing party" in the Header Data for a Contract (ME31K) filled in by default and modifyable.
Customizing (SPRO>Define Screen layout at Document Level) does not seem to resolve the problem.
Thanks a lot for your help.

For changing Partner functions in SPRO
SPRO>Materials Management>Purchasing>Partner Determination>Partner Settings in Purchasing Documents-->Define Partner Schemas
Assign Partner Schemas to Document Types
Check which parner scema assigned to your contract document type,Then you change partner scemas in Define partner functions (change/mandotary)

Problems in Global Outline Agreement

Hi friends,
                      We are using SRM 5.0 and R/3 4.7.I want to replicate contract to SRM 5.0 to R/3. For that I have to configure Global Outline Agreement. After creating and distributing GOA i am facing 2 errors. I got those errors from Transaction RZ20 -> SAP Enterprise Buyer Monitors - > Contract Management.
Errors are
Node name - SRD\Business to Business Procurement (500)\...\Contract Management\Contract Distribution
Date - 21.06.2008     Time - 14:37:45
System - SRD
Context - Business to Business Procurement (500)
Object Name - Contract Management
Short Name - Contract Distribution
Status - ACTIVE
Value - 3
Severity - 50
Status Set by - BBP
Status Set on - 21.06.2008
Status Set at - 09:07:45
Msg Class - SAP-T100
Msg Id - 000
Alert Text - Different processing times defined for BLAORD and CONDA
Var1 - 5600000014
Var2 - K77CLNT801       (backend Logical System)
Var3 - 0000000000000000
Var4 - 5600000014K77CLNT8010000000003          01
Node name - SRD\Business to Business Procurement (500)\...\Contract Management\Contract Distribution
Date 21.06.2008
14:37:45
System - SRD
Context - Business to Business Procurement (500)
Object Name - Contract Management
Short Name - Contract Distribution
Status - ACTIVE
Value - 3
Severity - 50
Status Set by - BBP
Status Set on - 21.06.2008
Status Set at - 09:07:45
Msg Class - SAP-T100
Msg Id - BBP_ADMIN 028
Alert Text - Application error in backend system K77CLNT801 (SRM outline agreement 5600000014)
Var1 - K77CLNT801      (backend Logical System)
Var2 - 5600000014
Var3 - 0000000000000000
Var4 - 5600000014K77CLNT8010000000003          01
I have done replication process of Purchase order from SRM to R/3.It is working fine.
I have done this configuration for GOA.
1.     Define GCTR transaction type in SRM.
2.     Define internal number range in SRM for the GOA that is the same as the external number range in the back end system for GCTR.
3.     Implement the badi BBP_CTR_BE_CREATE.
4.     Store, Plant, Material, Material group has been replicated from R/3.
I am getting those mentioned system message from Header Data -> Status
System Status
Complete
Created
Released
Distribution Incorrect
Document Completed
I am not using any conditions in item level.
How can I configure IDocs BLAREL for SRM and MM? I donu2019t have any idea?
Please help me to correct error .
Thanks in advance.

Hello,
check out notes 1053985 and 646903, that should solve your problem (especially the sections Mapping master data and Customizing data of note 646903).
Regards,
Andreas

Outline Agreement of FS Contarcts

Dear experts,
I'm struggling to try to understand how CRM Outline Agreements works.
Basically I can see that the standard solution privides two kinds of OA:
1. Promo Agreement: trans type DP, item categ DPI
2. Master Agreement: trans type MA, item categ MAF.
II succeeded in understand Promo Agreement, with which I can add third party subvention going to automatically add a Third Party Relationship on the FS contract, according to the access sequences defined in customizing.
Regarding Master Agreement, I already noticed that the determination on contract is customized differently in of respect DP, but is not such a problem.
I'm facing great difficulties in managing price agreements, payment structure and in reporting the results on the FS contract.
Do anyone has a "Best practice documentation" on how to manage and customize an Outline Agreement MA?
- Price agreements: It often gives errors (i.e.: when you try to maintain condition records pricing agreement the condition record is disappears from display during creation.).
I currently assigned a cond function group to the item category MAF to which is assigned a condition type with an access sequence containing the following accesses:
10     SAP00090
20     SAP00099
30     SAP00089
- Payment structure: I cannot insert flow categories in the payment structure of the OA item because the system gives the following error:
tem 1000: Payt struc.: You must enter a flow category before the first program run
Diagnosis
You have not entered a flow category for a step in the payment structure. You must enter a flow category before the first program run, otherwise you must change the flow category later. However, you are not then permitted to change the flow category group.
Procedure
Delete this row and insert a new row in the payment structure. Enter a flow category before the first program run.
When I create an FS Contract and the OA is determined in it, I cannot see any result such as, for example, the price agreement.
Do anyone knows how the outline agreement MA affects the FS contract?
Do anyone knows how to insert the payment structure on the outline agreement's item?
Thanks and regards
Dario

Hello,
Item category 'W' in a contract is not meant for automatic creation of a purchase order. It does not have a net price, where do you expect the system to pick this price from? Tax code only comes in later. Your error also talks about that.
The material group contracts can be used to keep track of orders so that they do not exceed a value limit.
In case, you do not know the material at the time of contract/ or have many similar type of materials use item category 'M' Material instead. In this you can specify price as well as tax code and use for auto POs.
Item Category/Account Assgt. Category in Contracts - Purchasing (MM-PUR) - SAP Library

To change the text of outline-agreement

Hi Experts,
Im using BAPI_CONTRACT_CHANGE function module to change outline agreement.When im executing this im getting the dump.Will you explain me how to use this fm to change the item text of outline-agreement.Will you please give the list of mandatory fields for this function-module.

IMPORTING
*"     VALUE(PURCHASINGDOCUMENT) TYPE BAPIMEOUTHEADER-NUMBER
*"     VALUE(HEADER) TYPE BAPIMEOUTHEADER OPTIONAL
*"     VALUE(HEADERX) TYPE BAPIMEOUTHEADERX OPTIONAL
*"     VALUE(VENDOR_ADDRESS) TYPE BAPIMEOUTADDRVENDOR OPTIONAL
*"     VALUE(TESTRUN) TYPE BAPIFLAG-BAPIFLAG OPTIONAL
*"     VALUE(TECHNICAL_DATA) TYPE BAPIMEOUTTECH OPTIONAL
*" EXPORTING
*"     VALUE(EXP_HEADER) TYPE BAPIMEOUTHEADER
*" TABLES
*"      ITEM STRUCTURE BAPIMEOUTITEM OPTIONAL
*"      ITEMX STRUCTURE BAPIMEOUTITEMX OPTIONAL
*"      ACCOUNT STRUCTURE BAPIMEOUTACCOUNT OPTIONAL
*"      ACCOUNTPROFITSEGMENT STRUCTURE BAPIMEOUTPROFITSEGMENT OPTIONAL
*"      ACCOUNTX STRUCTURE BAPIMEOUTACCOUNTX OPTIONAL
*"      DELIVERY_ADDRESS STRUCTURE BAPIMEOUTADDRDELIVERY OPTIONAL
*"      ITEM_COND_VALIDITY STRUCTURE BAPIMEOUTVALIDITY OPTIONAL
*"      ITEM_COND_VALIDITYX STRUCTURE BAPIMEOUTVALIDITYX OPTIONAL
*"      ITEM_CONDITION STRUCTURE BAPIMEOUTCONDITION OPTIONAL
*"      ITEM_CONDITIONX STRUCTURE BAPIMEOUTCONDITIONX OPTIONAL
*"      ITEM_COND_SCALE_VALUE STRUCTURE BAPIMEOUTITEMSCALEVAL OPTIONAL
*"      ITEM_COND_SCALE_QUAN STRUCTURE BAPIMEOUTITEMSCALEQUAN OPTIONAL
*"      ITEM_TEXT STRUCTURE BAPIMEOUTITEMTEXT OPTIONAL
*"      HEADER_TEXT STRUCTURE BAPIMEOUTTEXT OPTIONAL
*"      HEAD_COND_VALIDITY STRUCTURE BAPIMEOUTHEADVALIDITY OPTIONAL
*"      HEAD_COND_VALIDITYX STRUCTURE BAPIMEOUTHEADVALIDITYX OPTIONAL
*"      HEAD_CONDITION STRUCTURE BAPIMEOUTHEADERCOND OPTIONAL
*"      HEAD_CONDITIONX STRUCTURE BAPIMEOUTHEADERCONDX OPTIONAL
*"      HEAD_COND_SCALE_VAL STRUCTURE BAPIMEOUTSCALEVALUE OPTIONAL
*"      HEAD_COND_SCALE_QUAN STRUCTURE BAPIMEOUTSCALE OPTIONAL
*"      PARTNER STRUCTURE BAPIMEOUTPARTNER OPTIONAL
*"      PARTNERX STRUCTURE BAPIMEOUTPARTNERX OPTIONAL
*"      RELEASE_DOCU STRUCTURE BAPIMEOUTRELEASEINFO OPTIONAL
*"      EXTENSIONIN STRUCTURE BAPIPAREX OPTIONAL
*"      EXTENSIONOUT STRUCTURE BAPIPAREX OPTIONAL
*"      RETURN STRUCTURE BAPIRET2 OPTIONAL
FU BAPI_CONTRACT_CHANGE
Short Text
BAPI to Change a Purchase Contract
Functionality
BAPI for changing a purchase contract.
Notes
Master conditions
When creating outline agreements, you can specify only one period per variable key. This means that just one period can be specified for the document header (i.e. condition table A019). The same applies to each item (i.e. condition table A016) and to each item/plant combination (i.e. condition table A068).
You can use any periods. However they must not overlap for a variable key.
When conditions are changed, new condition records are nevertheless written.
Because volume rebate conditions are not taken into account in outline agreements, they are not processed.
No subitems (e.g. inclusive/exclusive bonus quantities, display, etc.) are taken into account.
The control key for quality management in procurement (EKPO-SSQSS) and the certificate category (EKPO-ZGTYP) are only taken into account to a certain extent. These two items of information are copied from the reference contract or material master, but cannot be changed; neither are any checks carried out for these two fields.
The revision level (EKPO-REVLV) cannot be changed because various quality management routines were not implemented.
Version management (Document Change Management) is not supported.
External services (planned or unplanned) are not supported.
The creation or changing of configurations is not supported.
Further information
When a purchase contract is changed (activity 02), the following authorization objects are checked:
M_RAHM_BSA Document type in contract
M_RAHM_EKG Purchasing group in contract
M_RAHM_EKO Purchasing organization in contract
M_RAHM_WRK Plant in contract
Parameters
PURCHASINGDOCUMENT
HEADER
HEADERX
VENDOR_ADDRESS
TESTRUN
TECHNICAL_DATA
EXP_HEADER
ITEM
ITEMX
ACCOUNT
ACCOUNTPROFITSEGMENT
ACCOUNTX
DELIVERY_ADDRESS
ITEM_COND_VALIDITY
ITEM_COND_VALIDITYX
ITEM_CONDITION
ITEM_CONDITIONX
ITEM_COND_SCALE_VALUE
ITEM_COND_SCALE_QUAN
ITEM_TEXT
HEADER_TEXT
HEAD_COND_VALIDITY
HEAD_COND_VALIDITYX
HEAD_CONDITION
HEAD_CONDITIONX
HEAD_COND_SCALE_VAL
HEAD_COND_SCALE_QUAN
PARTNER
PARTNERX
RELEASE_DOCU
EXTENSIONIN
EXTENSIONOUT
RETURN
Exceptions
Function Group
<b>rewards point for helpful answer.</b>

Tax value on Outline Agreement

I am very new to the concept of purchasing and outline agreements and below are some questions. Please help.
Should there be a tax value on outline agreements trxncode me32K?
Are they attached to purchase orders? and if so, how do you find out the PO attached to the contract(outline agreement).
Advance Thanks to those who can help and I will reward points.
Ladysap

Hi
1.For Outline agreement, Tax code is not mandatory. However, you can enter the same by selecting the line item and clicking "Item Details" (F2).
2. Yes, Contracts(Outline agreements) are attached to Purchase Orders. They are called Release Orders. To create a PO against a Contract, go to ME33K, give the Contrcat no and in the Menu go to Contract->Follow On functions->Release Order.
You can view the Pos attached to the Contract in ME33K. Select the item in the item overview and then choose Item -> Statistics -> Release documentation.
For further information on the release order (i.e. on the purchase order), choose Goto -> Release details.
If you wish the goods receipts and values of invoices received to be displayed for the item, choose Goto -> PO history. All GR and invoice documents are then listed.
For more information on Outline Agreements, pls visit http://help.sap.com/saphelp_erp2005vp/helpdata/en/75/ee0f5a55c811d189900000e8322d00/frameset.htm
Hope this clarifies.
Thanks

Invoicing Party In MIRO

Hi,
My problem is when I am doing MIRO the most of the fields in the header section loaded to the screen according to the PO one of the field is Invoice Party in the Detail Tab with label Inv. Party. But itu2019s open for input it means that user can change the invoice party and will go ahead. Now I donu2019t want that. user should not change the Invoice Party in MIRO for that I want to make this field only input field (Gray Filed).
I am trying to do same with Screen variant (SHD0) but there is some problem, so kindly request please arrane to give some document on this issue
If still have any doubt please revert back
Thanks in Advance
Warm Regards,
Mukesh Chejara

hi
best way is to change the message settings to ERROR.
WHen you change it the message must b coming like below
Account has been changed: Dependent data will be initialised
Message no. F5A119
so change this msg to ERROR with the help of ABAP guy.
check this thread
Problem in MIRO(IV)
for SHD0 take help of ur abaper
First you have to go in SHD0 and you will enter Screen Name ex
"miro" and the trasaction variant name you want to create (F5).
It will take you to MIRO and you will enter values. A window
will pop up asking you to check whatever you want to make
mandatory. Go through and save. Up at the top menu once you
get back to SHD0 initial screen, at the top menu, you will find
Deactivate Standard variant and again enter the Variant you want
to assign and go to the top menu and click assign variant. This
should work. It worked for me.
regards
kunal
Edited by: kunal ingale on Nov 14, 2008 8:02 AM

PR / Outline Agreement - UOM & Charges

Hi,
The client is giving services charges based on % (e.g., For recruiting services, when the candidate (of the vendor) is selected, then the recruiting vendor will receive 10% of that candidate's basic pay). The basic pays varies from position to position. For this scenario how the user has to prepare the PR (which UOM), and how to create outline agreement (i.e.,on which conditions/price).
Thanks,
Edited by: astudent on Dec 18, 2010 7:24 AM

Hi,
Create Service Masters of different position of candidate (like example: Service for Consultant, Service for Software engineer, Service for Sr. Consultant & Service for Sr. Software engineer with UOM is u201CEAu201D for all) & create a service vendor as recruiting service.
Create a service PR and then Service PO with service master with item category D & account assignment K & you can enter manually the price to be entering as 10% of amount of basic pay ( also you can enter service tax in invoice TAB 10.3%, if applicable) & save. Then you can do SES, MIRO and then payment to vendor.
NOTE:
If you want have outline agreement before PR& PO, you can create an outline agreement with ME31 with item category D and account assignment category U. But during creation of PR & PO wrt outline agreement you can enter account assignment category as you required ( K or P) by changing account assignment category U.
Regards,
Biju K

MM Outline Agreement Screen Flow

Our client has a requirement on contracts and scheduling agreements where they would like to see, displayed, the extended value of the line item and the total value of the outline agreement. I have located the fields needed and they seem to serve the client's requirement, but cannot determine how to get them to display on the outline agreement transactions (ME31,2,3....). The line item extended value field is found on EKPO_BRTWR; the document total is found on EKKO_RLWRT. Is there a way without doing a core mod that I can get these fields displayed on the documents on-screen?
Thanks!

hI,
For any document SAP flow will be header detail and item details.the aggrement total value comes in the header like for contract of type WK Value contract will have the total contract value , and will be available in the header screen of the aggrement . and the item cost will be in the item over view screen of the contract, with its qty and value. if you want furthur details like other conditions for that item , select that item and go to the conditions tab in the menu bar , then those details also will come.
Check the table EKKO for the header details and EKPO for the item details.
Regards,

Replacement of MIRO Invoicing Party (RBKP-LIFNR) with PO Invoicing Party

Hi,
As per one of our business requirement, we want to replace MIRO Invoicing Party (RBKP-LIFNR) with PO Invoicing Party (EKKO-LFRKE) for correct tax calculation during MIRO.
For that we tried to apply BAdis suggested as per SAP Note 1156325 - BAdIs in the Logistics Invoice Verification environment and others. But these BAdis are not enough useful to resolve above problem.
Pls suggest another BAdi / exit for above problem, which can replace MIRO Invoicing Party (RBKP-LIFNR) during MIRO .
Thanks & Regards,
Taral Patel

Hi,
Thanks for your reply.
below is our business scenario :
"PO is created on branch vendor (with a HO vendor mentioned in master).
While doing MIRO, the system automatically replaces the branch vendor with the Head
office vendor (as mentioned in master). The region taken for tax purpose is the region of the
HO vendor.
for above problem, I have been suggested Note 1156325 from the forum, but none of the BAdi seems feasible (checked with our SAP ABAP Consultant) for this requirement to replace MIRO Invoicing Party (RBKP-LIFNR) with PO Invoicing Party (EKKO-LFRKE).
It would be great help if u can suggest ny BAdi / exit for this requirement.
Thanks & Regards,
Taral Patel

Outline agreement - invoicing party at header

Similar Messages

Maybe you are looking for