Global discount in purchase order
Hello, experts
I have a customer who want to add a global discount (in value or % whatever) in a purchase order.
Do you know a way to do that?
Thanks
Loic
Hi Loic,
Do you want to maintain a price list for this or how you want this functionality to be performed.
Regards,
Samraj
Similar Messages
-
Printing discounts on purchase order
Hi Experts,
I have to print discounts from purchase order on the Adobe form for PurchaseOrder. But the discounts are not in the XML file.
I asked Cloud Support what I have to do for that, but they just said it's a consulting problem and not a technical problem and so they are not responsible.
For Sales there is an activity in File-tuning "Configure price strategy" where I can decide if I want to have discounts on the output or not. Is there something similar for purchasing? Or is there any other way?
Here an example screenshot attached.
kind regards,
Frank PohlmannHi Frank,
The fields are not part of the current standard solution. so you cannot bind them to the output form.
Regards,
Suresh -
Absolute Header Discount for Purchase Orders
Hi SAP Gurus,
Good day!
The scenario that I am testing is that I want to apply an absolute discount of USD1000 for a purchase order having 3 line items. When I use the available standard absolute header condition types and indicate the said amount, the system allocates USD1000 to each of the PO items. If that would be the case, then I have to enter USD1000/3 as header discount so that I can get the whole USD1000...Is there any other way so that I can just enter the whole amount without having to divide it by the number of PO
line items? Is there a setting that I need to consider in the condition type? Or is this really the way that SAP designed the condition types to behave? would you happen to know the governing reason why?
Also, I would appreciate it if you can provide me with some in depth training material regarding pricing procedures. The discussion on the standard MM course only briefly discusses the governing concepts.
Your immediate response is highly appreciated.
Best regards,
Pugnago to M/06...here in your absolute discount condition type check whether it is maintained as calculation type Fixed amount or not...if not then maintain it....it will automatically distribute
Otherwise
Check whether it is Header condition or Item condition...if item condition is not ticked then tick it....other wise you can create a new condition type also with item condition tick and maintain the same in your pricing procedure in M/08...
Now while processing PO enter the respective absolute discount amount in each line item rather than in the header condition tab...
Check http://wiki.sdn.sap.com/wiki/display/stage/MM-PRICINGUSINGCALCULATION+SCHEMA for pricing procedure..
Regards,
Indranil -
Input discounts in purchase orders
hello, my purchasing team is unable to input discounts into the purchase orders, we deducted the discount amount from the net value of each item manually and at the end the discount column remains 0, we hav adapted 2 doin this,how can we make it possible to input the discount amount in its column in the Purchase order?
regards,Adopt folliwnf steps:-
1) Maintaing the discount codnition type in the pricing procedure being used by the purchase order .
2)Kindly use the either of the condition type (as per relevant to the business scenario)
RB00 Discount (Value)
RC00 Discount/Quantity
RA00 Discount % on Net
RA01 Discount % on Gross
and than in the gross price condition type PB00 maintain the supplementary pricing procedure RM0002 which has these discount pricing condition type and than maintain these in Purchasing info record/contract .
Than you will be able to auotmatically get these discount along with gross price being pciked in the purchase order.
Regards
Amit
Edited by: Amit Kumar Pandey on Jan 25, 2011 5:07 PM -
Default header texts in purchase order
Hi,
I would like to ask you for help in following case.
I need to set default purchase header text when a new PO is created in me21n.
I found transaction VOTX where can be this done for sales order, but not for PO. Is there anything similar also in MM?
Maybe I could use user exits in MM06E005, but I didn't find the relevant structure which keeps header texts.
Third idea is to add header text fields into personal setting in me21n, where each user can define his own default texts but I have no idea how to do that.
I need to set default texts which are global for all purchase orders, so it has no sense to use Info record in this case.
Has anybody experience with this? I would appreciate any help. Thanks.Hi,
you can try to solve it using BADI ME_PROCESS_PO_CUST. The method open is suitable for you problem. Here is a quote from a BADI documentation.
The OPEN method enables you to do the following when opening a new
document:
o Import new data if the document was already posted to the database
o Initialize your own data when creating a new document
You get a reference for object with type IF_PURCHASE_ORDER_MM in this method. This class implements interface IF_LONGTEXTS_MM with methods like IF_LONGTEXTS_MMGET_TEXT and IF_LONGTEXTS_MMSET_TEXT. So you should be able to set long text for your new PO in this method. Check BADI documentation for more info.
Cheers -
Cash Discount in a purchase order
Hi,
I have a problem with Cash Discount in a purchase order .
When I create a purchase order in ME21N , and I need to put a cash discount in the condition of the header of the purchase order or in item detail, the line cash discount appears automatically when I create a new purchase order with the same material.
Anybody could tell me why the Cash Discount appears automatically?
Thanks a lot
KariHi,
There is a diference between cash discount and discount. Cash disocunt will never come in PO. It comes only during inoice.
The discount in PO is based on quantity. In your case it may ot be cash discount but a discount. It may come automatically because of one of the below reason.
1. If you create a PO wih reference to the PO, which is having discount.
2. If you maintain in Inforecord.
Regards,
Prabu -
Reporting on Purchase Order Discounts
Hi experts!
I read some threads about condition types etc. I have a requirement with my customer to not only enter a discount but also run reports on the given discount or at least a report which shows gross and net price.
Does anybody know if there are standard reports in SRM 5.0 which we could use? Or do we have to use BW for such kind of evaluations?
Does anybody have information about BW for SRM?
Many thanks for your help.
Best regards,
CorinneHi
<b>Please go through the following links -></b>
http://help.sap.com/saphelp_srm50/helpdata/en/ee/d9df3bbcce4b37e10000000a114084/content.htm
Re: SRM - problem in BW report execution - report id not geting passed
http://help.sap.com/saphelp_srm50/helpdata/en/14/15223862c3771be10000009b38f842/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/67/6e9746608221499322c93a03ffaf4e/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/75/c65d3a0eb60365e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/fd/dc804258544b76e10000000a155106/frameset.htm
PO Changes, PO date
http://help.sap.com/saphelp_srm50/helpdata/en/66/81b56c553b5840994ea041a5becd63/frameset.htm
Re: Report in EBP
Table links PO GUID and Confirmations in EBP
Item gross price condition / discount at backend PO
Re: SRM 4.0 Report's description ?
Influencing Condition Types in PO
Missing Acknowledgement in EBP Purchase order
Regarding condition types
Item gross price condition / discount at backend PO
Reports for Purchase Order
Re: Condition types from SRM to backend
Getting SC details using Backend Purchase Order
BBP_QUOT and Discount
Regards
- Atul -
Purchase order discount per row error
Dear all,
I have a client who gets the following error when trying to post an Purchase order:
"[Discount % per row] [Line 3], You are not permitted to perform this action"
The purchase order is a service order and no accounts have been selected. Also the discount field is not visible or active on the purchase order. The user is not authorized to add discounts but he has not done so in the first place. What could the problem be?
Regards,
Anthony NjagiHai!
Even if Discount field is not active in Row Level, for service Type Documents when i change Total value more than once that is calculating the difference to Discount.
Example:
First i entered Total as INR1000
I found that is wrong and changed to INR1200
The Difference between INR1000 and INR1200 will go to Discount.
To avoid this, ask user to type the amount in Unit Price Column instead of Total Column.
Regards,
Thanga Raj.K -
Discount not calculatig on Purchase order
hi,
maintained discount condition ZABC
when maintained in purchase order, it doesnt give effect anywhre?
Pls suggest
Alexhi alex
I am not clear on ur reply
If i get it right
when user manualy type <b>condition</b> system is not calculating but when ur selecting by F4 it is calculating correctly
Then check Spelling that he is typing for condition also check case of that condition( conditions are case sensitive )
Vishal... -
Gurus,
Need help in getting the source table of discount condition value in purchase order.
This is under the header condition tab. T-code: ME23N
Thanks in advanceDear Golddust,
1st go to EKKO table, enter PO number, then get the EKKO-KNUMV value, then go to table konv, and paste the KNUMV value in doc.condition, then execute, from there you can get all PO header condition.
Regards,
w1n -
Hi everybody ,
We need the Discount to be calculated automatically on the Total Order Value.
Its a promotion.
Useful suggestions will be rewarded.
Thanks
KartikHi pls follow the procedure below, Hope it will help u out
VOFM: ON PRICING
This note is an explanation of function "Maintain: Requirements and Formulas", which is also known as "VOFM".
By using descriptions and examples, this note explains how the VOFM function works in the R/3 Standard System, which objects are related to it and which restrictions exist.
Chapter 2.7 explains possible causes of errors and solutions for problems with the VOFM function.
To provide a good overview, this note is subdivided into the following sub areas:
1. General information
1.1 Definition of terms
1.2 Application areas
1.3 A frank word on the "source code responsibility"
2. Technology
2.1 Introduction
2.2 Namespaces
2.2.1 SSCR object registration
2.3 Structure of a VOFM object
2.3.1 Include file with ABAP form routine
2.3.2 Table entries in TFRM and TFRMT
2.4 Calling VOFM objects
2.4.1 VOFM object carrier
2.5 Activation, generation and RV80HGEN
2.6 Transport
2.7 FAQs: Possible causes of errors and problems
Technical field names are displayed in angle brackets [].
Note that this note only explains the mode of operation of the VOFM in an R/3 Standard Core System.
For R/3 industry solutions or Add-Ons the VOFM function displays a different behavior in subareas, however, this is not dealt with in this note.
Additional key words
VOFM, SAPMV80H, TFRM, TFRMT, RV80HGEN, XPRA, formulas, requirements, data transport routine, copy routine, data transfer.
Cause and prerequisites
1. General information
1.1 Definition of terms
Depending on the business processes used it may be necessary to influence the standard behavior of R/3 applications. For that purpose the VOFM function provides a corresponding environment in order to be able to develop and manage customer-specific logic simply.
The system stores the objects generated via the VOFM in the Customizing of the respective application area
(Pricing, message determination and so on) and its programs call the objects correspondingly.
Also SAP delivers certain functions in the form of VOFM objects.
Consequently, the VOFM is an exit technology as explained in more detail in Note 381348.
1.2 Application areas
Typical VOFM objects are requirements, formulas and data transfer routines.
These are used in processes of the purchase order, the delivery, billing, price determination, material determination, message determination, the free goods, the pricing and of others.
In the entries of the R/3 core menu of Transaction VOFM you can find a precise overview of the supported application areas.
1.3 A frank word on the "source code responsibility"
As in user exits, in VOFM objects are many fields and tables available. Thus, the use of VOFM objects is very versatile and consequently also very critical under certain circumstances. For the use of "customer-specific" VOFM objects the statements in Note 381348 regarding the responsibility for customer enhancements (Maintenance responsibility, problems during the upgrade and so on) apply. Read this note carefully before you decide on the use of customer-specific VOFM objects.
Errors and data inconsistencies that are caused by improper application or implementation of VOFM objects are not processed by the SAP Support but exclusively within the framework of the Consulting that has to be purchased separately.
2. Technology
2.1 Introduction
A VOFM object is uniquely defined via characteristics "group indicator" [GRPZE] and "group number" [GRPNO].
Here the group indicator, technically represented by a character field of length 4, is the logical connection to the calling environment.
Examples:
ABED copying requirement in the order
ADAT data transfer in the order
PBED requirements pricing
CASC Data transfer for sales activities
PBEK requirements account determination
CHRG requirements batches
REAK archiving for orders
VFCL Multi-dimensional scales
You can find all defined group indicators in the allowed values of the "GRPZE" domain in the ABAP Dictionary (Transaction SE11).
The group number can have a value from 1 to 999.
Exceptions are group indicators "PSTK" (= group key routine pricing) and "TDAT" (= data transfer for texts). For these the system can only assign group numbers from 1 to 99.
2.2 Namespaces
The VOFM has separate number ranges in order to distinguish VOFM objects delivered by SAP from customer-specific VOFM objects. These number ranges are often also called "VOFM namespaces".
However, note that this is not a "real namespace" that is protected by corresponding entries in system table "TRESC" (= reserved names for Customizing tables and Customizing objects).
Instead, only the VOFM logic itself does the definition and check of the number ranges.
The following list displays the customer number ranges sorted according to group indicators:
Indicator Name Number range customer
FOFU Subsequent functions 900 - 999
PSTK Group key routines 50 - 99
TDAT Data transfer routines f. texts 50 - 99
all other group indicators 600 - 999
In Note 356737 you can find more information on the available VOFM number ranges.
2.2.1 SSCR object registration
VOFM objects are subject to SSCR registration (= SAP Software Change Registration).
The reason for that is the necessity that every VOFM object is physically assigned to that SAP development class, from whose programs a corresponding jump into the VOFM object later occurs.
If you use the VOFM interface the system makes the assignment automatically. An assignment of customer-specific development classes is not possible.
2.3 Structure of a VOFM object
A VOFM object consists of the following parts:
Include file with ABAP form routine
TFRM table entry
TFRMT table entry
2.3.1 Include file with ABAP form routine
In the ABAP form routine the desired function is programmed.
Example pricing value formula number 001:
Include name : FV64A001
Form routine : FRM_KONDI_WERT_001
Implementation: * * Profit margin considering rebate agreements
form frm_kondi_wert_001.
xkwert = komp-kzwi3 - komp-wavwr.
endform.
Dependending on the selected group indicator, the group number and the system type (SAP or customer system), the system assigns and generates the include name and form routine name automatically.
For this reason, standard routines delivered by SAP generally have a different structure of the include name than customer-specific routines.
Example:
SAP standard value formula for the pricing
=> prefix FV64A + object number with 3 places from 'SAP namespace'
=> for example FV64A001
Customer-specific value formula for the pricing
=> prefix RV64A + object number with 3 places from 'customer namespace'
=> for example RV64A905
2.3.2 Table entries in TFRM and TFRMT
The entries in tables TFRM and TFRMT belonging to a VOFM object are used for the status management and assignment. The system always analyzes them if the user calls Transaction VOFM or if a generation operation occurs (for details refer to section 2.5).
The system generates exactly one TFRM table entry per VOFM OBjekt. In this TFRM entry the following information is stored:
Group indicator GRPZE
Group number GRPNO
Routine 'active' indicator AKTIV_TFRM
Application KAPPL
Date of the last generation GNDAT
Time of the last generation GNZEI
Examples:
GRPZE GRPNE AKTIV_TFRM KAPPL GNDAT GNZEI
PBED 001 X V 06 13 2001 09 06 39
TDAT 001 X 06 13 2001 09 06 39
CHRG 003 X 06 13 2001 09 06 39
The meaning of group indicators and group numbers has already been dealt with.
The 'active indicator' controls whether a VOFM object is 'active' or 'inactive'. Active VOFM objects have characteristic value AKTIV_TFRM = 'X', inactive objects have characteristic value AKTIV_TFRM = initial.
VOFM objects flagged as 'active' are 'known' to the calling program logic, that means they were included in the main program of the 'calling program' and can thus be addressed and
processed during the runtime.
You cannot delete VOFM objects that are still 'active'. In this case you have to reset the active indicator manually before.
The content of the 'Application' field serves to filter the relevant VOFM objects in various display functions and Customizing functions.
Example: Condition value formula 010 'Relevant Price'. This formula has characteristic value 'MS' for the 'Application' field (= External Services Management purchasing). Therefore the object is not open for selection in the input help during the maintenance of pricing procedure SD (Transaction V/08), because this is a Customizing transaction assigned to application 'V' (= Sales and Distribution).
Storing an application key is optional.
The generation date and the generation time record the time of the last registration of the VOFM object (the object carrier, refer to section 2.4.1).
In addition to the respective TFRM entry a VOFM object can have 'n' entries in table TFRMT. The entries are used for the storage of language-dependent object descriptions, which are structured as follows:
- Language key [SPRAS]
- Group indicator [GRPZE]
- Group number [GRPNO]
- Description [BEZEI]
Examples:
SPRAS GRPZE GRPNO BEZEI
D PBED 001 Regulierer abweich
E PBED 001 Different payer
The system supplies the language key automatically with the logon language of the user during the creation of a new VOFM object.
The length of the object description is limited to 20 characters.
Important! A VOFM object is only consistent if both the Include file with ABAP form routine and a corresponding TFRM table entry exist. Entries in table TFRMT are optional.
2.4 Calling VOFM objects
As mentioned above, VOFM objects are called directly by the application logic of R/3 standard programs. Technically this is implemented by ABAP statement 'PERFORM ... IN PROGRAM'. With the aid of this statement you can specify both the name of the subroutine and the main program dynamically (during the runtime).
Example: Call of a condition value formula from the pricing
if xkomv-kofrm ne 0. <<< formula reference existing?
xkwert = xkomv-kwert. <<< act. value in work variable
frm_kondi_wert-nr = xkomv-kofrm. <<< set up object names
perform (frm_kondi_wert) in program saplv61a if found. <<<CALL
xkomv-kwert = xkwert. <<
endif.
In the example above the subroutine is determined by the contents of variable 'FRM_KONDI_WERT'; the main program, which is to be searched for the form routine, is SAPLV61A.
If the called routine is not known in the main program, a program termination with the title 'PERFORM_NOT_FOUND' occurs.
Therefore some users of the VOFM technology call ABAP statement 'PERFORM ... IN PROGRAM' together with the addition 'IF FOUND', which has the effect that a jump into the form routine is only executed if this in fact exists in the main program. This does indeed prevent a program termination, however, the result of the overall process may deviate from the
result expected by the user, because in this case the system does not execute the source code implemented in the VOFM object.
2.4.1 VOFM 'object carrier'
Object carriers are required to make a VOFM object 'known' in the main program of the calling program (refer to section 2.4). The object carrier is integrated in the main program of the calling program as an independent include (for example SAPLV61A, SAPMV45A and so on).
Example: Inclusion of object carriers for word processing in SD
documents; Program 'SAPLV45T'
System-defined Include-files. *
INCLUDE LV45TTOP. "Global Data
INCLUDE LV45TDEF.
INCLUDE LV45TUXX. "Function Modules
INCLUDE LV45TNNN. <<< 'carrier' copy requirements for texts
INCLUDE LV45TENN. <<< 'carrier' copy routines for texts
Every active VOFM object (for an explanation on the active indicator refer to section 2.3.2) must be registered in the 'carrier'.
The system writes standard VOFM objects delivered by SAP directly into the 'carrier', VOFM objects from the number range reserved for customers (refer to section 2.2 'Namespaces') are sorted into a 'sub-include' included in the carrier.
Exactly one carrier exists per group indicator. The names of all defined object carriers are hard-coded in program MV80HF0A, form routine 'AKTIVIEREN_TRAEGER_SETZEN'.
Here the names of the sub-include for customer-specific VOFM objects belonging to the main carrier are also defined.
Example: Carrier object 'FV63ANNN' for the registration of condition basis formulas in the pricing (Program SAPLV61A)
FV63ANNN
<<< main
carrier-include
|-INCLUDE RV63ANNN. "User-Routinen <<< sub-include customer objects
| |- INCLUDE RV63A910. "Customer specific
| |- INCLUDE RV63A911. "Customer specific
| |- INCLUDE RV63A912. "Customer specific
| |- ...
|- INCLUDE FV63A001. "Volume
|- INCLUDE FV63A002. "Net value
|- INCLUDE FV63A003. "Net Price
|- INCLUDE FV63A004. "Net Value Plus Tax
|- INCLUDE FV63A005. "KZWI1
|- ...
Because the content of the VOFM object carriers is automatically created source code, you should avoid manual changes to them.
SAP notes, which suggest manual changes to the object carriers, are therefore also incorrect. However, if you nevertheless receive such a note to solve a problem, contact the SAP
Support with a reference to this note.
2.5 Activation, generation and RV80HGEN
The 'activation' is the inclusion of an VOFM object in an object carrier. A 'deactivation' results in the removal of the VOFM object from the object carrier.
The overall process for the creation of a current object carrier is often called 'generation'.
Generally the activation or generation fall into three types.
- Individual activation
- Collective activation
- Generation of object carriers via report RV80HGEN
The 'individual activation' causes the registration of an individual VOFM object in the corresponding object carrier. Which object carrier is relevant is determined with the aid of the group indicator and the group number. In addition to the entry of the VOFM object in the object carrier the system writes the date and time of the generation into table TFRM (refer also to section 2.3.2).
You can start the individual activation only manually. It is always always executed when a user selects a line within the VOFM editing interfaces and afterwards selects activity
'Activate' from the 'Edit' menu.
The 'collective activation' causes the registration of all VOFM objects that belong to a certain group indicator. Analog to the individual activation the system determines the relevant object carrier automatically and writes date and time into table TFRM. The 'collective activation' is a process which you can start also only manually. For this purpose, choose activity
'Activate all' from the 'Edit' menu.
During the generation via report RV80HGEN the system sets up the object carriers of all defined group indicators again. However, the system includes only those VOFM objects that have set the 'active' indicator in the corresponding TFRM table entry. Nonactive VOFM objects are not included in object carriers during the generation via report RV80HGEN.
Due to the quantity of the data to be processed,
the generation via RV80HGEN can take between 0,5 and >5 minutes (depending on the system and the constellation).
Because the RV80HGEN is defined as 'XPRA', it is executed automatically during a system upgrade.
You can also use this XPRA feature for the transport of VOFM objects in order to implement an automatic update of the object carriers after the import of VOFM objects into the target system (section 2.6 provides more details on the transport).
Both the collective activation and the activation via report RV80HGEN technically revert to the program components of the individual activation. For the separate control of the individual activation types form routine AKTIVIEREN_EINZELN (Include MV80HF0A) has a 'USING' parameter, which can have the following characteristic values:
'E' Activate individually
'A' Activate all (= collective activation)
' ' Deactivate individually
During the generation via RV80HGEN the system executes a collective activation for every group indicator sequentially, that means a call of form routine
AKTIVIEREN_EINZELN with characteristic value 'A'.
2.6 Transport
If you want to transfer VOFM objects from one system (= source) into another system (= target), this is generally made with an object transport.
As of Release 4.0, the VOFM function has a connection to the SAP 'Change and Transport System' (CTS) in order to simplify the transfer process for the user.
By the transport connection the system automatically adds newly created or changed VOFM objects to the object list of a transport request which was selected by the user before.
All steps necessary for the execution of a VOFM transport are described in detail in Note 22808 'Transferring formulas'. Note that steps 1-4 are only needed
if the VOFM maintenance environment providesno automatic connection to the transport system or if you want to combine a transport request manually. In any case you must execute step 5, regardless of how the transport request was created.
In addition to Note 22808, Note 385067 contains an overview for releases >= 4.6C regarding which sorts of tasks and object entries are required in a
transport request (depending on the activity carried out (create/change/activate/deactivate/delete)) in order to transport a VOFM object successfully. -
Payment by letter of Credit against Purchase order
When we are purchasing from Foreign Vendors , we need to open a Letter
of credit (LC) .
Depending on the terms of Purchase order , Vendor will discount it /get
payment from Bank on submitting LC and other necessary documents.
Vendor's Bank, at appropriate Time will send the same to Customer's Bank
How to mapped this scenario in SAP-MM and FI .
Activities required to be updated against Purchase order :
(1) Payment Terms : 100 % against LC on delivery
(2) History should reflect LC opened - Date and Bank Name which
Vendor has suggested, our company's Bank Name
(3) LC discounted details
(4) LC payment due date to our company Bank - as Procurement needs
to inform to Finance for this.
Any help will be highly appreciated.
Thanks and Best Regards,When we are purchasing from Foreign Vendors , we need to open a Letter
of credit (LC) .
Depending on the terms of Purchase order , Vendor will discount it /get
payment from Bank on submitting LC and other necessary documents.
Vendor's Bank, at appropriate Time will send the same to Customer's Bank
How to mapped this scenario in SAP-MM and FI .
Activities required to be updated against Purchase order :
(1) Payment Terms : 100 % against LC on delivery
(2) History should reflect LC opened - Date and Bank Name which
Vendor has suggested, our company's Bank Name
(3) LC discounted details
(4) LC payment due date to our company Bank - as Procurement needs
to inform to Finance for this.
Any help will be highly appreciated.
Thanks and Best Regards, -
Assigning free goods in a purchase order.
Hi,
I have to generate a report which will display the purchase order no for each condition record created in mbn1, and for each purchase order no it has to fetch the free goods assigned, eligible and remaining.
i have created a condition record for a vendor, with the following particulars,
if the vendor e.g ven1 purchases material e.g mat1
min qty = 100
free goods qty = 10
add. free goods = 2
calculation method is prorated
and the type is Inclusive.
But when i try to create a purchase order for that vendor ven1 for 200 qty of mat1, the gross price being calculated is for 200 qty, but it should be calculated for the quantity excluding the free goods qty.
What might be the reason, do i have to do any configuration in SPRO, if so guide me with the steps or can you help me in solving this problemHi,
I have maintained the condition record because i have checked the enry in the table KOTN001.
i have also maintained the settings for discount in kind as follows.
1. MAINTAIN DISCOUNT IN KIND DEPENDENCIES
I) Field Catalog.
BSTME,
EKORG,
EKOKZ
LIFNR,
MATNR
WERKS
ii). Display Free Goods
Table no 001 which has all the above mentioned fields.
2. DEFINE ACCESS SEQUENCE AND DISCOUNT-IN-KIND TYPES.
i) Maintain Access Sequence
Ac.sq DESC
NR00 Free Goods
Accesses Ac Tab Desc REQ
10 1 Info Record: Plant-specific 1
per order unit
20 2 Info record per order unit
Access 10's Fields.
Fields Condition I/O Doc.str Doc.field Long field Label
BSTME, I KOMP SAME
EKORG, I KOMK AS
EKOKZ I KOMP CONDITION
LIFNR, I KOMK
MATNR I KOMP
WERKS I KOMP
Source of constant Init
should i specify any values for source of constant and select the check box init, if so why?
Access 20's Fields.
same as 10 except the field werks, which is not included in the condition.
ii) Define free goods type.
ctyp name ac.sq validfrom validto
NR00 Free Goods NR00 2 (First 2(End of
day of the the current
month) year)
3.DEFINE AND ASSIGN DISCOUNT-IN-KIND SCHEMA
i) Maintain Free Goods Schema
Procedures
Usage N
Application M
Procedure Desc
NR0001 Free goods ( purchasing )
Control Data
Step Cntr Ctyp Description Requirement
10 0 NR00 Free goods 1
ii) Determine Free Goods Schema
Gr Gr Schema
0001 Standard order NR0001
0001 Retail vendor NR0001
Are the configuration which i have done is perfect for my scenario, if not, please can you help me in proceeding further.
Thank You. -
PO 'No goods receipt possible for purchase order'
Hi gurus!
While trying to make Confirmation of a PO in the SRM Portal the user is getting the error 'No goods receipt possible for purchase order'
The scenario used is Classic, so PO is replicated directly to the R/3 system.
Any idea why this is happening?
Thanks a lot!Hi, thanks for the quick reply!
Where i can check the Item category?
I found a field called 'subitem category' but it's blank
with this possible values:
1 Variant
2 Discount in kind: inclusive bonus qty.
3 Empties
4 Discount in kind: exclusive bonus qty.
5 Prepack item
6 Display item
7 Set item
8 Interchangeable items (IBU: A&D)
9 Pre-packing (SLS items)
H GT Bill of Material, Header Relevant
I GT Bill of Material, Item Relevant
About PO type i think it's EC (doc_type?), in R/3 is shown as EBP PO
I checked in backend system, in the item details > Delivery and the 'Goods Receipt' is checked. -
KEY FIGURE: Effective purchase order value & K.F "No. of Purch.Orders"
Yo my fellow Gurus,
Got a problem, when executing listcube on the Info-Cube 0PUR_C01 - I see the data/amounts in the column for "Effective purchase order value" / 0ORDER_VAL. But when running the query with the Key Figure I just get "0"
I tried the option of adding the Process Keys not allocated in the Routine list of keys, yet still nothing has popped in the query, and heres the routine after additonal keys added:
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
INCLUDE RS_BCT_MM_UPDATE_RULES.
$$ end of global - insert your declaration only before this line -
FORM compute_data_field
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING COMM_STRUCTURE LIKE /BIC/CS2LIS_02_SCL
RECORD_NO LIKE SY-TABIX
RECORD_ALL LIKE SY-TABIX
SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BI0/V0PUR_C04T-ORDER_VAL
RETURNCODE LIKE SY-SUBRC
ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line -
fill the internal table "MONITOR", to make monitor entries
IF ( COMM_STRUCTURE-PROCESSKEY = '001' or "Bestellung
COMM_STRUCTURE-PROCESSKEY = '011' or
*change of keys
COMM_STRUCTURE-PROCESSKEY = '015' or
COMM_STRUCTURE-PROCESSKEY = '005' or
COMM_STRUCTURE-PROCESSKEY = '025' or
COMM_STRUCTURE-PROCESSKEY = '041' or
COMM_STRUCTURE-PROCESSKEY = '051' or
COMM_STRUCTURE-PROCESSKEY = '061' or
*change of keys
COMM_STRUCTURE-PROCESSKEY = '021' or
COMM_STRUCTURE-PROCESSKEY = '004' or "LP
COMM_STRUCTURE-PROCESSKEY = '014' or
COMM_STRUCTURE-PROCESSKEY = '024' )
AND COMM_STRUCTURE-BWAPPLNM EQ 'MM'
AND COMM_STRUCTURE-ORDER_VAL <> 0.
perFORM LOC_CURR_CONVERT
USING COMM_STRUCTURE-ORDER_VAL
COMM_STRUCTURE-DOC_DATE
COMM_STRUCTURE-ORDER_CURR
COMM_STRUCTURE-LOC_CURRCY
COMM_STRUCTURE-EXCHG_RATE
CHANGING RESULT.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
else.
RETURNCODE = 4.
endif.
if abort is not equal zero, the update process will be canceled
This seems to be also the issue with my other Key Figure "No. of Purch. Orders" except here it the just comes up blank / 0 . This is to some the number of pos per plant for the month. So it's not storing anything but running via an interface and then with the aid of the routine loading the count into the cube:
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA: ...
$$ end of global - insert your declaration only before this line -
FORM compute_data_field
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING COMM_STRUCTURE LIKE /BIC/CS2LIS_02_HDR
RECORD_NO LIKE SY-TABIX
RECORD_ALL LIKE SY-TABIX
SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BI0/V0PUR_C04T-NO_PUR_ORD
RETURNCODE LIKE SY-SUBRC
ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line -
fill the internal table "MONITOR", to make monitor entries
if COMM_STRUCTURE-HDRPROCESS = '01' "Bestellung
AND COMM_STRUCTURE-no_hdr <> 0.
result value of the routine
RESULT = COMM_STRUCTURE-no_hdr.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
else.
RETURNCODE = 4.
endif.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM.
Please advise the way forward.
Thanks,
Ishaamwhat do u want?
Maybe you are looking for
-
I just purchased a MAC.. but have tons of video filmed in MP4. I have 2 questions. 1) I used Wondershare Video Converter to convert to MOV in HD 1920x1080 which is what I filmed in. When I bring it into FCP the video and audio have to be rendered.. e
-
Error in notification - "character string buffer too small"
Hi All, Hope everyone is doing great... I have issue with one of the procedure which sends out status email for the reports. Below is the code. It worked fine from last six months but today it failed because of the length of characters (more reports
-
Format a windows hard disk for mac
Hi, I am trying to format an external windows hard disk for use with my new Mac. I am using Disk Utility. The disk was NTFS formatted, I erased it into HFS+ (mentioning that the operation was done in less than a minute). I tried this many times bu
-
Hello Forum, I am in a situation of planning implementation strategy for Global SAP HR implementation across 30 counties. Process to be implemented 1. Performanace management 2. Hiring and firing 3. Payroll 4. Manage Employee Info. 5. Recruting 6. ES
-
New ALSB3.0 install, WorkSpaceStudio "JVM terminated. Exit code=127"
I'm trying to get ALSB up and running on Oracle Enterprise Linux 5.2 32-bit. I have it installed and the QuickStart will start up. However, when try to launch WorkSpaceStudio I receive the following error: JVM terminated. Exit code=127 /root/bea/jdk1