Credit Memo Request configuration
Gurus,
Could you please explain the configuration of
- Sales document type credit memo request (VOV8)
- Releasing or Rejecting credite memo by person responsible and
If the value of the credit memo request is below a certain minimum limit
- Billing document type credit memo
Regards,
Ashish
Hi Ashish,
Goto VOV8 T.code and then Selct the Order type as CR and click on copyas or F6.
Create your own document type as "ZCR" etc... and maintain the billing block as "08".Maintain reference mandatory as "M".In general we are creating with reference to an invoice.
Save.
Goto T.Code "VOFA" and then select the billing document type as "G2" and click on copy as or F6.
Save with your own name as "ZG2" etc...
Assign this billing document to your ZCR in VOV8 under order related billing as ZG2.
Save.
When you create the creditmemo request with reference to an invoice the billing block will come as "08".
The authorised persons only can remove this block.This can be done using the workflow.When the value is more than certain amount then the mail will triggered into the authorised persons mail id in SAP.They can check and release it using SBWP T.Code.
Then one can create the creditmemo with reference to this credit memo request.
Regards,
Krishna.
Similar Messages
-
Creating credit memo request - V1 498 / missing order quantity
Hi Experts,
could any of You pls help me with a credit memo creation issue?
I credit memo needed to be created based on invoice, so configuration and copy control is done as usual, but I have a failure during CR order creation referring to an invoice F2.
I got an error message: V1 498 - Credit already exist for item... - and no qty is transferred to new document
I have gone thought the threads on Forum, but none of the suggested solution was appropriate to solve the issue:
- the document flow is updated in copy control ,
- I can no remove the schedule line flag at VOV7 - the order qty will be missed but target qty is used, and end up incompletition (VU 019 error messge), so billing is faile
- completition control set as B at VOV7,
Still have the problem
Could any of You pls help me - answers will be appreciated.V1 498 - Credit already exist for item...
What the above message means is that lines items have already been used as reference for the creation of credit memo request(s).
Create a new sales order, delivery and billing document. Then create credit memo request with reference to this new billing document and test.
In VTAF copy control, at item level, field "Pos./neg. quantity" dictates how the quantity in the source document is affected by copy control.
PS - I tried to create credit memo with reference to billing document (F2), there were no issues there. Therefore I am taking that the issue is with credit memo request (copied with ref to billing document F2) -
Setting up multiple billing blocks for a CMR - Credit Memo Request
I am trying to set a billing block for a credit memo request. The item category in VOV7 configuration only allows you to set one. I need to be able to set any of them and for it to block. If we do not use one; the system allows the credit memo to get created. If we choose the one that we configured in VOV7 it allows us to only use that one. The client needs to be able to select any billing block from the drop down when creating a credit memo request in VA01 instead of just one specific one. Is this possible? If so, where would I do this?
Surprising! when a billing block is applied in the sales document, then the system will NOT allow to create the billing document(in your case credit memo). Can you check in t.code OVV3, the billing blocks are assigned to billing types? After assigning, create a new document and test. The path is SPRO->Sales and distribution -> billing->billing documents ->define blocking reasons for billing->assign blocking reasons to billing types.
Regards, -
Dear Gurus ,
I hv created Four sales document types ,I maintained four different pricing procedures for each sales doc type .
Assigned different doc procedure indicator as follows .
Sales doc type doc pricing proc indicator Billing type
ZS1 A ZF1
ZS2 1 ZF2
ZS3 2 ZF3
ZS4 3 ZF4
Now i want to create credit memo request ,
DO is there any way that i hv to confgure only one credit memo request document for referreing above different billing types.
Because it is showing error for pricing procedure determination.
Pls suggest should I configure four different credit memo request for that or not .
Thanks in advance .
Anchal PawarDear Ms Pawar,
A single credit memo request may be configured in order to refer each of the billing types by appropriate settings in copy control, provided all the item categories and schedule line categories involved in the referring document are covered.
Further, a credit memo would not have an explicit pricing procedure, but would copy the procedure from the referred document.
Changes if applicable may be set in the copy control settings.
Trust I clarify.
Regards,
K Gopidas. -
Credit memo request with currency conversion to EURO
I have a requirement in which i need to create a Credit Memo Request for the newly created sales organisation using the old billing document number created for old sales organisation.New sales org will have its currency changed to EURO.I referred to a FM named 'Pricing' where the currency conversion is done.
The requirement is to get the current price in EURO from the price list instead of currency conversion to EUR.The current price has to be extracted from new pricelist.
Your inputs in this regard is highly appreciated.HI
Am not on SAP system now, so will try to give you
info with what i can recollect.
You can use FM: SD_SALESDOCUMENT_CREATE for creating
Credit Memo Request. Note that reference document and
reference type should be passed for identifying the
reference document as invoice. Please consider these as
initial inputs to explore on the same. Regarding the
pricing, it can be configured either at order type or
copy control to carry out new pricing so it can take
directly from condition records.
Hope the above info can help you in exploring on the same.
Kind Regards
Eswar -
REBATE CREDIT MEMO REQUEST -2CONDITION TYPE
HI ALL,
I am doing material rebate with my condition type ZZ02 n maintaing a rebate agreement for 1000 Rs- 50 Rs as my accruals. My accruals are Rs 200 after billing. Now when i am going and creating a rebate credit memo request, its not taking the Rs 200/- as the value rather 2 line items are generated with C. type ZZ02 with Rs 200 as my value(statuary) and another line item with (Rs 1000 *x quantity) which is the one it is taking.
PLs let me know where i could be wrong in my settings.
Rgds,
AmitDid by configuring rebate aggrement type.
-
How to update the status of Credit memo request as "Close" by putting reason of rejection
Dear All,
Our requirement is to close credit memo request, We already cancelled the subsequent document i.e. billing. In credit memo request we are trying to close it by putting "Reason of Rejection", but instead of closed is coming as " Being Process". I already did the required configuration at Item Level for G2N in VOV7, but still the status is "Being Process".
Please let me know if I m missing config.
Thanks,
Sumeet SahHi
Check this below link. I had faced this issue years ago and got a strange solution which is still applicable.
Open status of Credit Memo after rejecting all line items
Thank$ -
Creation of Credit memo Request using FM SD_SALESDOCUMENT_CREATE
Hi Guys,
I am using FM SD_SALESDOCUMENT_CREATE to create credit memo request from flat file.
we are using variant configuration and characteristic values for material are not being populated. Rest of the sales document is created but characteristic values are missing.
can any one help me if u have some information or some piece of code.
here is the code i am using.
LOCAL DATA DECLARATION
DATA: L_WA_ORDER_CFGS_VALUE TYPE BAPICUVAL,
L_WA_ORDER_CFGS_REF TYPE BAPICUCFG,
L_WA_ORDER_CFGS_INST TYPE BAPICUINS,
L_WA_ORDER_CFGS_PART_OF TYPE BAPICUPRT.
CONSTANTS: C_MARA TYPE CHAR10 VALUE 'MARA',
C_300 TYPE CHAR03 VALUE '300'.
IF FP_L_WA_CHAR-ITM_NUMBER <> FP_V_ITEM_OLD.
Build internal tables for material configuration
Configuration: Reference Data
L_WA_ORDER_CFGS_REF-POSEX = FP_L_WA_CHAR-ITM_NUMBER.
L_WA_ORDER_CFGS_REF-CONFIG_ID = FP_L_WA_CHAR-ITM_NUMBER.
L_WA_ORDER_CFGS_REF-ROOT_ID = FP_L_WA_CHAR-ITM_NUMBER.
APPEND L_WA_ORDER_CFGS_REF TO FP_I_ORDER_CFGS_REF.
Build internal table BAPICUINS
Configuration: Instances
L_WA_ORDER_CFGS_INST-CONFIG_ID = FP_L_WA_CHAR-ITM_NUMBER.
L_WA_ORDER_CFGS_INST-INST_ID = FP_L_WA_CHAR-ITM_NUMBER.
L_WA_ORDER_CFGS_INST-CLASS_TYPE = C_300.
L_WA_ORDER_CFGS_INST-OBJ_TYPE = C_MARA.
L_WA_ORDER_CFGS_INST-OBJ_KEY = FP_L_WA_CHAR-MATERIAL.
APPEND L_WA_ORDER_CFGS_INST TO FP_I_ORDER_CFGS_INST.
Configuration: Part-of Specifications
L_WA_ORDER_CFGS_PART_OF-OBJ_TYPE = C_MARA.
L_WA_ORDER_CFGS_PART_OF-CLASS_TYPE = C_300.
L_WA_ORDER_CFGS_PART_OF-OBJ_KEY = FP_L_WA_CHAR-MATERIAL.
APPEND L_WA_ORDER_CFGS_PART_OF TO FP_I_ORDER_CFGS_PART_OF.
FP_V_ITEM_OLD = FP_L_WA_CHAR-ITM_NUMBER.
ENDIF.
Configuration: Characteristic Values
Sales Document Item
L_WA_ORDER_CFGS_VALUE-CONFIG_ID = FP_L_WA_CHAR-ITM_NUMBER .
L_WA_ORDER_CFGS_VALUE-INST_ID = FP_L_WA_CHAR-ITM_NUMBER.
Characteristic Name
L_WA_ORDER_CFGS_VALUE-CHARC = FP_L_WA_CHAR-CHARC .
Characteristic Value
L_WA_ORDER_CFGS_VALUE-VALUE = FP_L_WA_CHAR-VALUE .
APPEND L_WA_ORDER_CFGS_VALUE TO FP_I_ORDER_CFGS_VALUE.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
CALL FUNCTION 'SD_SALESDOCUMENT_CREATE'
EXPORTING
SALES_HEADER_IN = FP_WA_ORDER_HEADER_IN
SALES_HEADER_INX = FP_WA_ORDER_HEADER_INX
BEHAVE_WHEN_ERROR = C_R
BUSINESS_OBJECT = 'BUS2094'
IMPORTING
SALESDOCUMENT_EX = L_SALESDOCUMENT
TABLES
RETURN = L_I_RETURN
SALES_ITEMS_IN = FP_I_ORDER_ITEMS_IN
SALES_ITEMS_INX = FP_I_ORDER_ITEMS_INX
SALES_PARTNERS = FP_I_ORDER_PARTNERS
SALES_SCHEDULES_IN = FP_I_ORDER_SCHEDULES
SALES_SCHEDULES_INX = FP_I_ORDER_SCHEDULESX
SALES_CONDITIONS_IN = FP_I_ORDER_CONDITIONS_IN
SALES_CONDITIONS_INX = FP_I_ORDER_CONDITIONS_INX
SALES_CFGS_REF = FP_I_ORDER_CFGS_REF
SALES_CFGS_INST = FP_I_ORDER_CFGS_INST
SALES_CFGS_PART_OF = FP_I_ORDER_CFGS_PART_OF
SALES_CFGS_VALUE = FP_I_ORDER_CFGS_VALUE
SALES_TEXT = FP_I_ORDER_TEXT.Hi, has your question be answered? What was the outcome / result?
-
Credit Memo Request and Credit Management
Hi, can anyone advise the following?
I noticed that sales values of the credit memo request is updated to the open delivery instead of open order in the credit master. Why is this so? Also, when i select a order order reason configured with fixed value '1' 'relevant for retro-billing, then the sales value is not updated. What's the purpose of this indicator in the configuration?
Thanks
PPhello, PP.
i don't have an answer yet. actually, i will add to your question.
a credit memo request is supposed to be not relevant for delivery. so why is this updating open delivery value? maybe it's SAP standard? maybe credit group 03 (delivery docs) was assigned to the credit memo request doc type? if so, why assign credit management to credit memo requests anyway?
regards. -
COPA Values in the Profitability analysis for a credit memo request
Hi All,
When I am trying to create an Invoice document for a Credit Memo request having a Configurable material , in the accounting document profitable analysis Profit Center view fields are not getting updated.
If we do the same thing for a reference material profit center view fields are getting updated properly.
What is the problem with the Configurable material.
Thanks in advance,
RajaMahiI would start fresh with a new sales order. When you create with reference both the return delivery and credit memo are created with reference to the return sales order. Here is an example document flow to clarify:
Document Date Qty/value UoM/Cur Overall proc. status
Return 60000077 / 10 08/25/05 10.000 EA Completed
. Returns Delivery 500000016 / 10 08/25/05 10.000 EA Completed
.. GD returns QI 4900030060 / 1 08/25/05 10.000 EA complete
.. Credit for Returns1 10000017 / 10 08/25/05 10.000 EA Completed
... Accounting document 10000017 08/25/05 10.000 EA Cleared -
Reg: Two credit memo for one credit memo request
HI expert,
The requirement here is related to warranty, payment thru credit memo, partial payment 90% first 10% after receipt of some required documents.
So need to configure for two credit memo with ref to one credit memo request, not based on qty.. we have worked on value part so no problem abt it.. will share it later, but at first we need to create two credit memo with ref to 1 Credit memo Req.
Please through some light....
Regard
PraveenHi,
You can use the BILLING PLAN for this
Just assign the TAO ITEM CATEGORY for you sales document type in VOV4 and maintain the Billing Plan dates while processing the Sales order.
Now you can create two Billing documents with reference to the Same order based on the BILLING PLAN dates maintained in the Sales ordre-Item-BILLING PLANT tab will appear .
There you can define the BILLING DATE and on that particular date you can create the Billings for one sales order.
Please check and revert back if you need frther details
regards,
santosh -
Copy control from Credit Memo request to Credit memo.
Dear SD Experts,
I have to create Credit Memo, for this I have to use copy control from Credit memo request (VA01) to Credit Memo (VFO1. Kindly suggest me how it can possible what config is requires to do this.
Regards,
Manzoor AhmadHi Manzoor,
Go to VTAF
Set target document type is credit memo and source document type is credit memo request and define the same in the copy control refer the standard one copy the same and configured (CR TO F1),
still if you need clarification please let me know,
Thanks and Best Regards,
Muralidharan S -
BAPI_SALESDOCU_CREATEFROMDATA, create credit memo request
hi all,
in which field of BAPI_SALESDOCU_CREATEFROMDATA needs to fill in, i need to create SO Credit memo request (CR doc type ) with reference to billing no , which field shall i put the billing no ?REPORT ZTEST_SO_CREATE .
Order Header
DATA: HEADER LIKE BAPISDHD1.
Internal Item Number Assignment
DATA: L_INA LIKE BAPIFLAG-BAPIFLAG.
Item Data
DATA: IT_ITEM LIKE BAPISDITM OCCURS 0 WITH HEADER LINE.
Document Partner
DATA: IT_PARTN LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE.
Schedule Line Data
DATA: IT_SIN LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE.
Conditions
DATA: IT_COND LIKE BAPICOND OCCURS 0 WITH HEADER LINE.
Configuration: Reference Data
DATA: IT_CUCFG LIKE BAPICUCFG OCCURS 0 WITH HEADER LINE.
Configuration: Instances
DATA: IT_CUINS LIKE BAPICUINS OCCURS 0 WITH HEADER LINE.
Part_of Entries of Several Configurations
DATA: IT_CUPRT LIKE BAPICUPRT OCCURS 0 WITH HEADER LINE.
CU: Reference Order Item / Instance in Configuration
DATA: IT_CUREF LIKE BAPICUREF OCCURS 0 WITH HEADER LINE.
Characteristic values of several configurations
DATA: IT_CUVAL LIKE BAPICUVAL OCCURS 0 WITH HEADER LINE.
*Number of Generated Document
DATA: L_SO LIKE BAPIVBELN-VBELN.
DATA: RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
START-OF-SELECTION.
Header data
PERFORM SUB_HEADER.
Internal Item Number Assignment
L_INA = 'X'.
Item Data
PERFORM SUB_ITEM.
Document Partner
PERFORM SUB_PARTN.
Schedule Line Data
PERFORM SUB_SIN.
Conditions
PERFORM SUB_COND.
Configuration: Reference Data
PERFORM SUB_CUCFG.
Configuration: Instances
PERFORM SUB_CUINS.
Part_of Entries of Several Configurations
PERFORM SUB_CUPRT.
CU: Reference Order Item / Instance in Configuration
PERFORM SUB_CUREF.
Characteristic values of several configurations
PERFORM SUB_CUVAL.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
ORDER_HEADER_IN = HEADER
INT_NUMBER_ASSIGNMENT = L_INA
IMPORTING
SALESDOCUMENT = L_SO
TABLES
RETURN = RETURN
ORDER_ITEMS_IN = IT_ITEM
ORDER_PARTNERS = IT_PARTN
ORDER_SCHEDULES_IN = IT_SIN
ORDER_CONDITIONS_IN = IT_COND
ORDER_CFGS_REF = IT_CUCFG
ORDER_CFGS_INST = IT_CUINS
ORDER_CFGS_PART_OF = IT_CUPRT
ORDER_CFGS_VALUE = IT_CUVAL
ORDER_CFGS_REFINST = IT_CUREF.
Check the
RETURN TABLE.
LOOP AT
RETURN WHERE TYPE = 'E' OR TYPE = 'A'.
EXIT.
ENDLOOP.
LOOP AT RETURN.
WRITE :/
RETURN-TYPE,
RETURN-ID,
RETURN-NUMBER,
RETURN-MESSAGE,
RETURN-LOG_NO,
RETURN-LOG_MSG_NO,
RETURN-MESSAGE_V1,
RETURN-MESSAGE_V2,
RETURN-MESSAGE_V3,
RETURN-MESSAGE_V4,
RETURN-PARAMETER,
RETURN-ROW,
RETURN-FIELD,
RETURN-SYSTEM.
ENDLOOP.
IF SY-SUBRC = 0.
Commit the work.
COMMIT WORK AND WAIT.
WRITE: / 'Document ', L_SO, ' created'.
ENDIF.
*& Form SUB_HEADER
text
--> p1 text
<-- p2 text
FORM SUB_HEADER.
Sales document type
HEADER-DOC_TYPE = 'ZOEM'.
Sales organization
HEADER-SALES_ORG = '1000'.
Distribution channel
HEADER-DISTR_CHAN = '12'.
Division
HEADER-DIVISION = '03'.
Sales group
HEADER-SALES_GRP = '001'.
Sales office
HEADER-SALES_OFF = '1000'.
Requested delivery date
HEADER-REQ_DATE_H = '20070701'.
HEADER-REQ_DATE_H = SY-DATUM.
Proposed date type
HEADER-DATE_TYPE = '1'.
Customer purchase order date
HEADER-PURCH_DATE = '20070701'.
HEADER-PURCH_DATE = SY-DATUM.
Sales district
HEADER-SALES_DIST = 'CC'.
Incoterms (part 1)
HEADER-INCOTERMS1 = 'EXW'.
Incoterms (part 2)
HEADER-INCOTERMS2 = 'XIAMEN'.
Terms of payment key
HEADER-PMNTTRMS = '1000'.
Date for pricing and exchange rate
HEADER-PRICE_DATE = '20070701'.
HEADER-PRICE_DATE = SY-DATUM.
Customer purchase order number
HEADER-PURCH_NO_C = 'atest'.
SD document category
HEADER-SD_DOC_CAT = 'C'.
Shipping conditions
HEADER-SHIP_COND = '02'.
Shipping type
HEADER-SHIP_TYPE = '07'.
HEADER-PURCH_NO_S = '1100511'.
ENDFORM. " SUB_HEADER
*& Form SUB_ITEM
text
--> p1 text
<-- p2 text
FORM SUB_ITEM.
Sales document item
IT_ITEM-ITM_NUMBER = '001000'.
Higher-level item in bill of material structures
IT_ITEM-HG_LV_ITEM ='000000'.
Item Number of the Underlying Purchase Order
IT_ITEM-PO_ITM_NO = '1000'.
Material number
IT_ITEM-MATERIAL = 'VD4'.
APPEND IT_ITEM.
IT_ITEM-ITM_NUMBER = '001001'.
IT_ITEM-HG_LV_ITEM ='001000'.
IT_ITEM-PO_ITM_NO = '1001'.
IT_ITEM-MATERIAL = 'CDX8004317R3J'.
IT_ITEM-CONFIG_ID = '000001'.
IT_ITEM-INST_ID = '00000001'.
APPEND IT_ITEM.
ENDFORM. " SUB_ITEM
*& Form SUB_PARTN
text
--> p1 text
<-- p2 text
FORM SUB_PARTN.
Partner function
IT_PARTN-PARTN_ROLE = 'AP'.
Customer number
IT_PARTN-PARTN_NUMB = '0000000090'.
Item number of the SD document
IT_PARTN-ITM_NUMBER = '000000'.
APPEND IT_PARTN.
IT_PARTN-PARTN_ROLE = 'VE'.
IT_PARTN-PARTN_NUMB = '0000000107'.
IT_PARTN-ITM_NUMBER = '000000'.
APPEND IT_PARTN.
IT_PARTN-PARTN_ROLE = 'SB'.
IT_PARTN-PARTN_NUMB = 'OEM'.
IT_PARTN-ITM_NUMBER = '000000'.
APPEND IT_PARTN.
IT_PARTN-PARTN_ROLE = 'AG'.
IT_PARTN-PARTN_NUMB = '0001100511'.
IT_PARTN-ITM_NUMBER = '000000'.
APPEND IT_PARTN.
ENDFORM. " SUB_PARTN
*& Form SUB_SIN
text
--> p1 text
<-- p2 text
FORM SUB_SIN.
Sales document item
IT_SIN-ITM_NUMBER = '001000'.
Schedule line
IT_SIN-SCHED_LINE = '0000'.
Schedule line date
IT_SIN-REQ_DATE = '07-01-2007'.
Date type (day, week, month, interval)
IT_SIN-DATE_TYPE = '1'.
Order quantity in sales units
IT_SIN-REQ_QTY = 5.
APPEND IT_SIN.
IT_SIN-ITM_NUMBER = '001001'.
IT_SIN-SCHED_LINE = '0000'.
IT_SIN-REQ_DATE = '07-01-2007'.
IT_SIN-DATE_TYPE = '1'.
IT_SIN-REQ_QTY = 5.
APPEND IT_SIN.
ENDFORM. " SUB_SIN
*& Form SUB_COND
text
--> p1 text
<-- p2 text
FORM SUB_COND.
Condition item number
IT_COND-ITM_NUMBER = '001000'.
Step number
IT_COND-COND_ST_NO = '000'.
Condition counter
IT_COND-COND_COUNT = '00'.
Condition type
IT_COND-COND_TYPE = 'VA00'.
Condition rate
IT_COND-COND_VALUE = 1.
Currency Key
IT_COND-CURRENCY = 'RMB'.
APPEND IT_COND.
IT_COND-ITM_NUMBER = '001000'.
IT_COND-COND_ST_NO = '000'.
IT_COND-COND_COUNT = '00'.
IT_COND-COND_TYPE = 'PR01'.
IT_COND-COND_VALUE = 1.
IT_COND-CURRENCY = 'RMB'.
APPEND IT_COND.
IT_COND-ITM_NUMBER = '001001'.
IT_COND-COND_ST_NO = '000'.
IT_COND-COND_COUNT = '00'.
IT_COND-COND_TYPE = 'VA00'.
IT_COND-COND_VALUE = 1.
IT_COND-CURRENCY = 'RMB'.
APPEND IT_COND.
IT_COND-ITM_NUMBER = '001001'.
IT_COND-COND_ST_NO = '000'.
IT_COND-COND_COUNT = '00'.
IT_COND-COND_TYPE = 'PR01'.
IT_COND-COND_VALUE = 1.
IT_COND-CURRENCY = 'RMB'.
APPEND IT_COND.
ENDFORM. " SUB_COND
*& Form SUB_CUCFG
text
--> p1 text
<-- p2 text
FORM SUB_CUCFG.
External item number
IT_CUCFG-POSEX = '001001'.
External Configuration ID (Temporary)
IT_CUCFG-CONFIG_ID = '000001'.
Instance Number in Configuration
IT_CUCFG-ROOT_ID = '00000001'.
APPEND IT_CUCFG.
ENDFORM. " SUB_CUCFG
*& Form SUB_CUINS
text
--> p1 text
<-- p2 text
FORM SUB_CUINS.
External Configuration ID (Temporary)
IT_CUINS-CONFIG_ID = '000001'.
Instance Number in Configuration
IT_CUINS-INST_ID = '00000001'.
Object type
IT_CUINS-OBJ_TYPE = 'MARA'.
Object key
IT_CUINS-OBJ_KEY = 'D'.
APPEND IT_CUINS.
IT_CUINS-CONFIG_ID = '000001'.
IT_CUINS-INST_ID = '00000002'.
IT_CUINS-OBJ_TYPE = 'MARA'.
IT_CUINS-OBJ_KEY = 'D2'.
APPEND IT_CUINS.
ENDFORM. " SUB_CUINS
*& Form SUB_CUPRT
text
--> p1 text
<-- p2 text
FORM SUB_CUPRT.
External Configuration ID (Temporary)
IT_CUPRT-CONFIG_ID = '000001'.
Instance Number in Configuration
IT_CUPRT-PARENT_ID = '00000001'.
Instance Number in Configuration
IT_CUPRT-INST_ID = '00000002'.
Part_of item number
IT_CUPRT-PART_OF_NO = '0280'.
Object type
IT_CUPRT-OBJ_TYPE = 'MARA'.
Object key
IT_CUPRT-OBJ_KEY = 'D2'.
APPEND IT_CUPRT.
ENDFORM. " SUB_CUPRT
*& Form SUB_CUREF
text
--> p1 text
<-- p2 text
FORM SUB_CUREF.
External item number
IT_CUREF-POSEX = '001001'.
External Configuration ID (Temporary)
IT_CUREF-CONFIG_ID = '000001'.
Instance Number in Configuration
IT_CUREF-INST_ID = '00000001'.
APPEND IT_CUREF.
ENDFORM. " SUB_CUREF
*& Form SUB_CUVAL
text
--> p1 text
<-- p2 text
FORM SUB_CUVAL.
External Configuration ID (Temporary)
IT_CUVAL-CONFIG_ID = '000001'.
Instance Number in Configuration
IT_CUVAL-INST_ID = '00000001'.
Characteristic name
IT_CUVAL-CHARC = 'ZS1_LV_HEIGHT'.
Characteristic Value
IT_CUVAL-VALUE = '02'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_TOP'.
IT_CUVAL-VALUE = '04'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_LV_BOTTOM'.
IT_CUVAL-VALUE = '01'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_BOTTOM'.
IT_CUVAL-VALUE = '01'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_CB_DOOR'.
IT_CUVAL-VALUE = '01'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_FIXED_PT'.
IT_CUVAL-VALUE = '01'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_EK6'.
IT_CUVAL-VALUE = '01'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_EK6_VENDER'.
IT_CUVAL-VALUE = '01'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_AUX'.
IT_CUVAL-VALUE = '02'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_INTERL'.
IT_CUVAL-VALUE = '01'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_CA'.
IT_CUVAL-VALUE = '01'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_DXN_Q'.
IT_CUVAL-VALUE = '02'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_CAP_DIV'.
IT_CUVAL-VALUE = '02'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_PACK'.
IT_CUVAL-VALUE = '02'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_PAINT'.
IT_CUVAL-VALUE = '02'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_AUX'.
IT_CUVAL-VALUE = '02'.
APPEND IT_CUVAL.
IT_CUVAL-CONFIG_ID = '000001'.
IT_CUVAL-INST_ID = '00000001'.
IT_CUVAL-CHARC = 'ZS1_RECTIFIER'.
IT_CUVAL-VALUE = '01'.
APPEND IT_CUVAL.
ENDFORM. " SUB_CUVAL -
Credit Memo Invoice - Configurable Material
I have a sales order with configurable material and the appropriate invoice.
Sales Order has type "credit memo request" and the invoice is a "_credit memo_".
It is not possible to release the document to Accounting/COPA.
Error message is "Error reading the material cost estimate for sales order xxxx".
What can I do to proceed? Which Customizing settings are necessary? Because it is correct, that there is no material cost estimate because the material is calculated while creating the sales order.
Thanks for your feedback in advance!
Best regards,
Pamela Glatz
Application Services/COHI,
Please check whether u have configured any costing key with setting for reading the cost estimate of the material.
As you said, the cost estimate of the material doesnt come in your scenario, there should not be any configuration in copa to read the cost estimate(thru costing key)
Regards
Sudhakar Reddy -
Credit memo request release according to values
Hello Gurus,
How can I configure for following function:
If the value of the credit memo request is below a certain minimum limit, then it can be released automatically by the system, and make the definition of the point at which the check is carried out and the employee responsible dependent upon the value of the credit memo request.
thanks very much!Using the workflow, you can represent the whole business process, with all the people involved, for approving credit memo requests within your company. This enables you to process credit memo requests simply and efficiently.
If you do not use the workflow, the system does not control the process flow.
In your case, you should have a workflow such that if the value of a credit memo request is below a minimum value, the system automatically releases it for billing by removing the billing block.
If the credit memo request exceeds a certain value, the system automatically informs the employee responsible. She or he receives a work item in their inbox and can process it directly from there.
You need to configure the settings in Customizing for the workflow and create an organizational plan for this.(you may use other methods other that org plan. A workflow consultant may give you further details)
you should configure such that when you create credit memo requests, the system normally sets a billing block, which prevents it from being billed.
You create the billing block for credit memo requests in customizing for Sales and Distribution when you define the order type (Sales and Distribution ->Sales ->Sales Documents-> Sales Document Header ->Define sales document types)
Maybe you are looking for
-
What is the use of variant in the alv report
hello all, what is the use of variant in the alv report
-
How to increase Memory and Java Heap Size for Content Server
Hi, My content server is processing requests very slowly. Over performance is not good. I have 2 GB of RAM any idea what files I can modify to increase the Java Heap Size for the Content Server. If I increase the RAM to 4 or 6 GB where do I need to m
-
Can't Open Folder in XMLSPY after B1iSN PL11 Upgrade.
Hi, I've recently upgraded to B1iSN PL 11. I've followed all the steps in the guide . and it seems that the login method has changed due to the upgrade. when I try to edit/view my BIU with the previously setup configuration in XMLSPY I get the follow
-
High frequency power measurements
Hey, I'd like to know if there are developments in measuring electrical high frequency signals with labview without using an extern power analyser. At the moment i'm using a yokogawa power analyser but i'd like to know if it's possible to log HF sign
-
Time Machine error "not enough disk space"
I just recently updated to Mavericks and Time Machine won't work. Sounds like it's a common problem, but I've gone back a month in the forum and haven't found my exact issue yet. In my case, I get an error message that claims I don't have enough di