Pricing conditions changed should get approval

Dear Experts,
We have a requirement. A report should run every night which should output the changes in an existing condition record. The result of the report should be sent to the respective manager for approval.
How can we configure this please help.
Thanks in advance..

Hiii
Here is standard T-code available for the same, AUT10, Kindly explore to meet ur requirement.
Thanks and regards
Shambhu Sarkar

Similar Messages

How to handle the different pricing conditions changes in BI.

Dear Friends
can any one send me Regarding
How to handle the different pricing conditions changes in BI.
Thanks & Regards
Ramana

Hi,
Take a look at the 0sd_o06 ODS and 2lis_13_vdkon datasource for sales billing conditions.
http://help.sap.com/saphelp_nw70/helpdata/EN/36/8188408bc0bb4de10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/7f/0f8c4037fba62be10000000a1550b0/frameset.htm
Regards.

Automatic PO adjustment for pricing condition changes sap

Hello SAP users,
How to prevent automatic PO adjustment for pricing condition changes to purchase order items that are marked for deletion. Please respond.
Thanks

Hi,
Check the settings in below configuration:
SPRO>MM>Purchasings>Conditions>Automatic document adjustment-->Control doc. adjustment.
SAM

Block Sales order if pricing condition changed manually (no delivery)

Hi,
Requirement is to block sales orders for review by a manager if pricing condition amount is changed manually. Only a manager should be able to review and release the sales order for billing. There is no delivery, item is service.
Thanks

Hi,
This can be achieved as follows:
1) SAP Standard updates the field KOMV->KSTEU for respective price condition type as soon as its changed Manually.
2) Through enhancement automatically delivery block should be set at Sales Order Header, for which User (Sales End User) should not have rights to change.
3) Respective Sales Manager should receive a mail regarding the same.
Point '3' can be done manually i.e user will request respective Manager to do the needful.
RB.

Pricing condition records should not be picked up

Hi,
I have configured a scenario for Supplementary Invoice for which I created a new sales order type. The requirement is such that this order type should not pick the pricing condition records that have been created in VK11. Please suggest how can this be configured.
Do I have to use any Userexits, if so which one?
Regards,
Abhishek

As mentioned by you, you have created a new Sales Order Type, you can create a new document pricing procedure, based on which you can determine a new pricing procedure.
To configure new Document Pricing Procedure:
IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Define Document Pricing Procedure. (Maintain the new Document Pricing Procedure in new Sales Order Type)
Maintain a new Pricing Procedure, maintaining the Condition Types as manual. Maintain the determination of Pricing Procedure appropriately.
Pricing Procedure Determination:
In SD, Pricing Procedure is determined (T.Code: OVKK) based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Pricing Procedure Configuration:
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka

LSMW Pricing Condition changes

Hi,
I need to create a LSMW to change pricing condiitons in condition type PR00 for access sequence table 006 (Price List Type/Currency/Material). I did the following:
1. Defined Object attributes Standard/Batch Direct Input 0070 (Condition record) Program Name RV14BTCI and Program type B (Batch). Method is 000.
2. Where do I define that the new records have to go into this table 006? Will it be in the source structures? Source fields? Can anyone explain me step by step how this will work? And what will be the subsequent steps? The documentation I have on LSMW isn't much help unfortunately and is very generic. I need specific solution/steps to this pricing condition table. Any guidance on it?
Thanks a lot.

Hi Kevin
Pl. check this link on LSMW pricing :
<a href="http://sap-img.com/sap-data-migration.htm">LSMW</a>
<a href="http://sap-img.com/sd001.htm">to upload pricing conditions</a>
Pl reward if it helps.
Thanks & Regards
Sadhu Kishore

Pricing condition record not getting executed in Sale order!

hello all
I was trying to process a sale order, when i enter the material, system giving me a message "ZINV" condition type missing. i have checked v/08 there is "check - tick mark" for 'zinv' condition type and I have maintained the condition record.
It is still giving me the same error.
any one can help me?
thanks

Same as above.
If you are getting the error "Mandatory Pricing condition XXX is missing". All you have to do it select the item and then hit pricing icon on the lower section of your screen and then enter the missing condition in the table displayed in front of you and then enter a price etc.
This message can be removed by customizing the pricing procedure and removing the 'Mdt' flag.
Also make sure the condition type has been marked for manual update in the condition detail section.

Remove from Billing Plan after Pricing Condition change

Hi all,
I am trying to implement code to deduct from the last date of a billing plan once a pricing condition type is used. Currently, when you enter the pricing condition it spreads the deduction amount across all of the dates in a billing plan.
If we use VOFM, where would I define this? I've created code in the Pricing Requirements but table FPLT is not available to me and I don't know how to only remove from the last date instead of all.
Thanks in advance!

Hello,
If you have necessary authorization to change the Pricing Date in Invoice, please go ahead.
Change the Pricing date in Invoice, go to Conditions tab & update the Pricing. System will fetch Condition Records as on that date.
Hope this helps,
Thanks,
Jignesh Mehta

Pricing Condition Type should split the Value

Hello Gurus,
I am working on Billing Plan for Contracts. In the contract I enter the condition type with Rs.24000. The same net value should split in the billing plan by months for 12 months as Rs2000.00. Any inputs on this?
Regards
Venkat

Hello,
In v/06 make a new condition type for 'Monthly Value'.Eg. ZP00
Cond. class   A Discount or surcharg
Calculat.type A Percentage
maintain vk11 for ZP00 as 8.333%
In the pricing procedure , add the new condition type after main price condition as below.
STEP    CNTR CTyp         DESCRIPTION                     FROM    TO    MAN MDT             STAT
100             0     PR00     Price                                                               CHECK         CHECK
200          0     ZP00     Monthly Value     100
please check the same and revert back.
Thanks & Regards,
Hegal

Statistical condition types not getting displayed in invoice

We have configured the tax collected at source (TCS) condition types and make them as statistical in the pricing procedure. Now, the issue is when we are using them the values for these condition types are getting calculated correctly as the total value is correct but in the invoice their individual values are not getting displayed.
In the analysis also we can see that the condition records are found but being statistical condition they should get displayed in the invoice as only the correct total value will not serve the purpose, please help
Thanks & regards
Puneet Agrawal

Hi
Keep a break-point (hard) in these program lines and debug and see that whether the condition type(KSCHL) related to Taxes is appearing here or not.
If the condition type for taxes is coming then you can print the taxes.
First check the related condition type for Taxes in T685 table and see here in the code.
Reward points for useful Answers
Regards
Anji

Pricing condition in sales order-issue

Experts,
i am facing a very strange issue, functional consultant
did some configuration ,such that when header of
sales order have condition type ,let say some 'ZXX',
this pricing conditon should be applicable to all
the schedule line with pricing condition as 'ZXX' where material in schedule line is let say 'ZPP',that mean
these should only be applicable for material type
'ZPP',we are facing strange issue , when scheule line no
10 is having material 'ZPP' ,then pricing conditon is
working fine('ZXX'),but if scheule line no 10 is having
material other than 'ZPP' and if scheule line no 20
is having material 'ZPP' ,then for scheule line no 20
pricing condition is not getting copied from header

goto tcode - vk13
note that [A]--sequence for plant /material
note that --sequence for plant /material/cafgroup
enter ur pricing condition type and
for the plant/material combination etc.. [A]-
may be in the access sequence ur consultant ave given it to a new sequence say plant/material/caf group .. --
like this
suppose say item 10 is for option [A] so access sequence is for this only ..cause material is now in plant/material
now say item 20 is for option so
material at line item 2 will fall under this sequence ..
cumulatively u need to get the total ..
now if the material is same in line 10 20 , u will have to fetch the values from both the tables in sequence and not one table will store the values ..
cause sequence pass for the material is now [A] and 
rememebr that per classification the values are stored in diff table like a906 ,, a90*..
in order to fetch that u need to get it from the tables of classification
and then cumulate it ..
this is important ..
regards,
VIjay.
Message was edited by: Vijay

Pricing Conditions in Invoice

Hello All,
Thank you all for a remarkable support and knowledge you are sharing in this forum. Appreciate you all.
Well here is a situation , when we are processing Invoices - a particular pricing condition we are getting an error. The error is : Pricing condition found but not set". Can any one please suggest what might be the possible problem and how to fix it. This is a Tax condition.
Thanks & Regards
Sai

Hi Sai
This is a very standard error.
THis comes due to the timing difference between the pricing date and the date on which the condition record was maintained.
Consuder the order is created on 10.12.2007 and condition record created on 11.12.2007. Now if u go to the invoice then it will show condition record found but not set. In this case you can do update pricing again. If this doesnt work then you will need the pricing date in invoice or service rendered date in sales order to the date after the condition records maintained and then do repricng.
Hope this helps. Reward accordingly.
Kind Regards
Sandeep

Custom pricing condition not getting triggered automatically in CRM 4.0

Hi
The custom discount pricing condition created in R/3 is active in R/3 and is getting triggered for Sales Orders created in R/3.
I have downloaded the same pricing conditon from R/3 to CRM 4.0 i am able to trigger it manually in CRM service transaction. But i need the condition to be triggered automatically for the pricing group.
Your inputs are highly solicited
Thanks
Padma

Hi Padma,
did you enable the condition download from ERP to CRM already? Did you run the initial condition customizing download and the initial condition master data download successfully (check also the application log in SLG1)?
In addition, you should be aware, that for any condition customizing change in ERP you need to rerun the initial customizing download (there is no delta download) and that you need to refresh the IPC customizing buffer, which is automatically done once a day by default.
Best Regards,
Michael

How to get xkomv-kwert (condition value) from a pricing condition ZZP1

Hi experts,
   I have a pricing condition zcust that I need to modify in the sales order.   The calculation of ZCUST is dependent on the condition value in another price condition ZZP1.   The price for ZZP1 is a fixed amount of $6 which is split among line items in the order.    In sapmv45A, when the code hits userexit_save_document_prepare, the value of xkomv-kwert (condition value) exist.   In other user-exits in sapm45A, I was unable to find xkomv-kwert. My question is: How can I find the value of xkomv-kwert as i don't know how ZZP1 is calculated ?? There is no routine attached to ZZP1.
    THE ZCUST has a routine 993 which is similar to 3.   Here in program saplv61A, i was trying to get xkomv-kwert for ZZP1 but unable to get any data.   Can anyone suggest where i can get the data (xkomv-kwert) for ZZP1 in saplv61a ?
I looked at userexit_xkomv_bewerten_end in saplv61a but it does not help.
XKomv-kbetr always has data.    If i have ZZP1 data, then i can modify ZCUST.
Many thanks.
Joyce

Hi Jelena,
In VOFM, it is Formula/Condition Base Value for routine 993.   In Pricing Procedure, it falls in column "Base Type" for 993.
Let's see if i can simplify this: In a sales order with 2 line items:
               prices                    Amt                      Condition Value (USD)
Line 10     ZS1   sell price     2.30                                 1150
                 ZPP1 charge        6.36                                 3.40 (note the distribution **)
                 ZL1                      3                                      3
                ZR1 %                  1.000%                            11.50
                ZR2                      0.01                                   5
                Suggested price = 2.35                             1172.90
                  ZCUST               2.34                                1170
                  total price            2.34                               1170
Note: The ZCUST price is wrong. It is missing the ZPP1 charge which is 3.40. Zcust should be 1170 + 3.40 = 1173.40
Line 20     ZS1   sell price     25                                 1000
                 ZPP1 charge        6.36                                 2.96 (note the distribution **)
                 ZL1                      3                                      3
                ZR1 %                  1.000%                            10
                ZR2                      0.01                                   0.6
                Suggested price = 25.41                              1016.56
                  ZCUST                   25.34                           1013.60 (should be 1013.60 + 2.96)
               Total price                25.34                            1013.60
You can see the ZCUST is calculated incorrectly. The routine calculate zcust as $1170 and $1013.60 for each item which did not include the distribution amount of ZPP1 ($3.40 and $2.96).
When i debug the routine, the xkomv-kwert is zero.   I am trying to get $3.40 and $2.96 so i can add to to zcust in the routine.
Am trying to determine in saplv61A at which include that i can see #3.40 and $2.96 for both line items in xkomv-kwert.
Then maybe i can modify the routine or saplv61A so it shows the correct zcust price after entering the 2 line items in the sales order create (VA01) ?     Can you pls suggest ?
If i make the changes in USEREXIT_SAVE_DOCUMENT_PREPARE, then user cannot see the correct zcust until the order is saved. This would be too late to know the zcust price ahead of time.
Pls view in the Edit mode... i see my texts have been compressed.
Many thanks
Joyce
Edited by: Joyce Chan on Jul 9, 2009 10:24 PM
Edited by: Joyce Chan on Jul 9, 2009 10:25 PM

Change Pricing Condition for an item with CRM_ORDER_MAINTAIN

Hi community,
I try to change an existing condition with the function module crm_order_maintain.
Everything looks fine, no error no dump, but no success
The condition stays the same!
Can anybody find a solution for this?
Heres my report so far:
*& Report ZTEST_PRICING2
REPORT ztest_pricing2.
DATA: lt_guid TYPE crmt_object_guid_tab,
 lt_item TYPE crmt_object_guid_tab,
 lt_saved TYPE crmt_return_objects,
 lt_pridoc TYPE crmt_pric_cond_t,
 ls_pridoc TYPE crmt_pric_cond,
 lt_pricom TYPE crmt_pridoc_comt,
 ls_pricom TYPE crmt_pridoc_com,
 lt_header TYPE crmt_orderadm_h_comt,
 lt_input TYPE crmt_input_field_tab,
 ls_input TYPE crmt_input_field,
 ls_input_fn TYPE CRMT_INPUT_FIELD_NAMES,
 ls_cond_chg TYPE prct_cond_external_change,
 ls_cond TYPE PRCT_COND_DU,
 lt_pricing_i TYPE CRMT_PRICING_I_WRKT.
PARAMETERS: lv_head TYPE crmt_object_guid DEFAULT 'C4C61C4E35DDF306E10000000A024089'.
PARAMETERS: lv_item TYPE crmt_object_guid DEFAULT '09C71C4E35DDF306E10000000A024089'.
PARAMETERS: lv_kbetr TYPE prct_cond_rate DEFAULT '100'.
INSERT lv_head INTO TABLE lt_guid.
INSERT lv_item INTO TABLE lt_item.
CALL FUNCTION 'CRM_ORDER_READ'
EXPORTING
 it_header_guid = lt_guid
 it_item_guid = lt_item
* IV_MODE =
* IV_ONLY_SPEC_ITEMS =
* IT_REQUESTED_OBJECTS =
* IV_NO_AUTH_CHECK =
* IT_ITEM_USAGE_RANGE =
* IV_SUBITEM_DEPTH = -1
* IT_OBJECT_FILTER =
* IV_ONLY_CHANGED_OBJ = FALSE
* IV_STATUS_H_CHECK_RELEVANCE = FALSE
IMPORTING
 et_pridoc = lt_pridoc
 et_pricing_i = lt_pricing_i
* CHANGING
* CV_LOG_HANDLE =
EXCEPTIONS
 document_not_found = 1
 error_occurred = 2
 document_locked = 3
 no_change_authority = 4
 no_display_authority = 5
 no_change_allowed = 6
 OTHERS = 7.
IF sy-subrc <> 0 AND lt_pridoc IS NOT INITIAL.
WRITE: / 'ERROR'.
EXIT.
ENDIF.
READ TABLE lt_pridoc INDEX 1 INTO ls_pridoc.
IF sy-subrc <> 0.
WRITE: / 'ERROR'.
EXIT.
ENDIF.
READ TABLE ls_pridoc-pric_cond INTO ls_cond WITH KEY kschl = 'PB00'.
IF sy-subrc <> 0.
WRITE: / 'ERROR'.
EXIT.
ENDIF.
ls_input-ref_guid = lv_head.
ls_input-ref_kind = 'A'.
ls_input-objectname = 'PRIDOC'.
ls_input_fn-fieldname = 'WAERS'.
INSERT ls_input_fn INTO TABLE ls_input-field_names.
ls_input_fn-fieldname = 'KBETR'.
INSERT ls_input_fn INTO TABLE ls_input-field_names.
INSERT ls_input INTO TABLE lt_input.
ls_pricom-ref_guid = lv_head.
ls_pricom-ref_kind = 'A'.
*ls_pricom-PRICING_TYPE = 'B'.
*ls_pricom-pricing_procedure = 'ZZMTA'.
ls_pricom-pric_cond[] = ls_pridoc-pric_cond[].
MOVE-CORRESPONDING ls_cond TO ls_cond_chg.
ls_cond_chg-waers = 'EUR'.
ls_cond_chg-kbetr = lv_kbetr.
INSERT ls_cond_chg INTO TABLE ls_pricom-cond_change.
APPEND ls_pricom TO lt_pricom.
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
EXPORTING
 it_pridoc = lt_pricom
CHANGING
* ct_orderadm_h = lt_header
 ct_input_fields = lt_input
EXCEPTIONS
 error_occurred = 1
 document_locked = 2
 no_change_allowed = 3
 no_authority = 4
 OTHERS = 5.
IF sy-subrc <> 0.
EXIT.
ENDIF.
CALL FUNCTION 'CRM_ORDER_SAVE'
EXPORTING
 it_objects_to_save = lt_guid
IMPORTING
 et_saved_objects = lt_saved
* ET_EXCEPTION =
* ET_OBJECTS_NOT_SAVED =
EXCEPTIONS
 document_not_saved = 1
 OTHERS = 2.
IF sy-subrc EQ 0.
COMMIT WORK AND WAIT.
ELSE.
ROLLBACK WORK.
ENDIF.
regards
Markus

Hello Jordi,
The example below is whereby i was trying to copy all the pricing condition on one document to another and deleting what's not present on the source document.
You can used this piece of code to adapt your requirement.
CALL FUNCTION 'ZCRC_FM_COPY_PRICE_COND_ALL'
 EXPORTING
id_object_guid_src = <fs_el_con_guid>
id_object_guid_dest = <fs_el_so_guid>
id_commit = abap_false
 EXCEPTIONS
not_allowed = 1
error_occured = 2
OTHERS = 3.
PERFORM f_recup_donnees USING id_object_guid_src
 id_object_guid_dest.
PERFORM f_modif_condition_prix USING id_object_guid_src
 id_object_guid_dest.
PERFORM f_header_copy_pricing using id_object_guid_src
 id_object_guid_dest.
FORM f_recup_donnees USING pd_object_guid_src TYPE crmt_object_guid
 pd_object_guid_dest TYPE crmt_object_guid.
DATA:
 lt_header_guid TYPE crmt_object_guid_tab.
INSERT pd_object_guid_src INTO TABLE lt_header_guid.
INSERT pd_object_guid_dest INTO TABLE lt_header_guid.
CLEAR: gt_orderadm_i, gt_doc_flow.
CALL FUNCTION 'CRM_ORDER_READ'
 EXPORTING
 it_header_guid = lt_header_guid
 IMPORTING
 et_doc_flow = gt_doc_flow
 et_orderadm_i = gt_orderadm_i
 EXCEPTIONS
 document_not_found = 1
 error_occurred = 2
 document_locked = 3
 no_change_authority = 4
 no_display_authority = 5
 no_change_allowed = 6
 OTHERS = 7.
IF sy-subrc NE 0.
 RAISE error_occured.
ENDIF.
" F_RECUP_DONNEES
FORM f_modif_condition_prix USING pd_guid_src TYPE crmt_object_guid
 pd_guid_dest TYPE crmt_object_guid.
DATA : ld_pd_handle_src TYPE prct_handle,
 ld_pd_handle_dest TYPE prct_handle,
 lt_komv_print_src TYPE prct_cond_print_t,
lt_komv_print_dest TYPE prct_cond_print_t,
 ls_komv_print_dest LIKE LINE OF lt_komv_print_dest,
 ls_komv_print_src LIKE LINE OF lt_komv_print_src,
 lt_cond_chg TYPE prct_cond_print_t,
 lt_cond_chg_insert TYPE prct_cond_print_t,
 ls_cond_chg TYPE prct_cond_print,
 ls_cond_chg_tmp TYPE prct_cond_print,
 ls_input_fields TYPE crmt_input_field,
 lt_input_fields TYPE crmt_input_field_tab.
DATA : bal_log TYPE balloghndl,
 lt_item_ret TYPE prct_item_ret_t,
 lt_cond_ret TYPE prct_cond_print_t,
 ld_data_changed TYPE xfeld,
 gv_decimal TYPE usdefaults-dcpfm,
 ld_lines TYPE i,
 ld_ajout_cond TYPE abap_bool.
FIELD-SYMBOLS : <fs_orderadm_i_dest> TYPE crmt_orderadm_i_wrk,
<fs_orderadm_i_src> TYPE crmt_orderadm_i_wrk,
 <fs_cond_chg> TYPE prct_cond_print,
<fs_cond_chg_insert> TYPE prct_cond_print.
* Début Ajout CD1K904313-001.
DATA: ld_guid_src TYPE crmt_object_guid.
FIELD-SYMBOLS: <fs_doc_flow> TYPE crmt_doc_flow_wrk.
* Début Ajout CD1K904313-001.
* Verrouillage des documents source et destinataire
PERFORM f_lock_document USING pd_guid_src.
PERFORM f_lock_document USING pd_guid_dest.
*Récupérer le pricing handle des documents
* Document source
CALL FUNCTION 'CRM_PRIDOC_GET_HANDLE_OW'
 EXPORTING
iv_header_guid = pd_guid_src
 IMPORTING
ev_pd_handle = ld_pd_handle_src
 EXCEPTIONS
error_occurred = 1
handle_determination_error = 2
 orgdata_error = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 RETURN.
ENDIF.
* Document destinataire
CALL FUNCTION 'CRM_PRIDOC_GET_HANDLE_OW'
 EXPORTING
 iv_header_guid = pd_guid_dest
 IMPORTING
 ev_pd_handle = ld_pd_handle_dest
 EXCEPTIONS
 error_occurred = 1
 handle_determination_error = 2
 orgdata_error = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 RETURN.
ENDIF.
* A ne pas traiter les postes de type ZPDF
DELETE gt_orderadm_i WHERE itm_type = 'ZPDF'.
LOOP AT gt_orderadm_i ASSIGNING <fs_orderadm_i_dest> WHERE header = pd_guid_dest.
 REFRESH : lt_komv_print_src,
 lt_komv_print_dest,
lt_cond_chg,
lt_cond_chg_insert.
* Début Modif CD1K904313-001.
* Récupérer le guid de l'item liée au item destinataire.
 READ TABLE gt_doc_flow ASSIGNING <fs_doc_flow> WITH KEY objkey_b = <fs_orderadm_i_dest>-guid.
 CHECK sy-subrc EQ 0.
 ld_guid_src = <fs_doc_flow>-objkey_a.
* READ TABLE gt_orderadm_i ASSIGNING <fs_orderadm_i_src> WITH KEY header = pd_guid_src
* number_int = <fs_orderadm_i_dest>-number_int.
* Fin Modif CD1K904313-001.
* Récupérer les pricing document
 IF sy-subrc EQ 0.
* Document source
 CALL FUNCTION 'PRC_PD_ITEM_SHOW'
 EXPORTING
 iv_pd_handle = ld_pd_handle_src
* iv_item_no = <fs_orderadm_i_src>-guid "Supression CD1K904313-001
 iv_item_no = ld_guid_src "Addition CD1K904313-001
 IMPORTING
 et_komv_print = lt_komv_print_src
 EXCEPTIONS
 non_existing_handle = 1
 non_existing_item = 2
 ipc_error = 3
 OTHERS = 4.
 ENDIF.
* Document destinataire
 CALL FUNCTION 'PRC_PD_ITEM_SHOW'
 EXPORTING
 iv_pd_handle = ld_pd_handle_dest
 iv_item_no = <fs_orderadm_i_dest>-guid
 IMPORTING
et_komv_print = lt_komv_print_dest
 EXCEPTIONS
 non_existing_handle = 1
 non_existing_item = 2
 ipc_error = 3
 OTHERS = 4.
* Modification et Suppression des conditions de prix
 LOOP AT lt_komv_print_dest INTO ls_komv_print_dest .
 CLEAR: ls_cond_chg,
 ls_komv_print_src.
 MOVE-CORRESPONDING ls_komv_print_dest TO ls_cond_chg.
* Rechercher la condition sur le document source
 READ TABLE lt_komv_print_src INTO ls_komv_print_src WITH KEY kschl = ls_komv_print_dest-kschl
zaehk = ls_komv_print_dest-zaehk. "CD1K904313
 IF sy-subrc EQ 0.
 ls_cond_chg-kbetr_prt = ls_komv_print_src-kbetr_prt.
 ls_cond_chg-kwert = ls_komv_print_src-kwert.
 ls_cond_chg-kinak = ls_komv_print_src-kinak.
 ELSEIF ls_cond_chg-kschl IS NOT INITIAL.
 CLEAR ls_cond_chg.
 CONTINUE.
 ENDIF.
* Format décimal
 CASE gv_decimal.
 WHEN space. "format N.NNN,NN
 REPLACE ALL OCCURRENCES OF '.' IN ls_cond_chg-kbetr_prt WITH ','.
 WHEN 'Y'. "format N NNN NNN,NN
 REPLACE ALL OCCURRENCES OF '.' IN ls_cond_chg-kbetr_prt WITH ','.
 ENDCASE.
 INSERT ls_cond_chg INTO TABLE lt_cond_chg.
 CLEAR ls_cond_chg.
 ENDLOOP.
* Ajout des conditions de prix
 LOOP AT lt_komv_print_src INTO ls_komv_print_src WHERE kschl IS NOT INITIAL.
 CLEAR: ls_cond_chg, ld_lines, ls_komv_print_dest, ls_cond_chg_tmp, ld_ajout_cond.
* Vérifier la présence de la condition sur le document destinataire
 READ TABLE lt_komv_print_dest INTO ls_komv_print_dest WITH KEY kschl = ls_komv_print_src-kschl
zaehk = ls_komv_print_src-zaehk. "CD1K904313.
 IF sy-subrc EQ 0.
 CLEAR: ls_cond_chg, ls_komv_print_dest.
 CONTINUE.
 ELSE.
 DESCRIBE TABLE lt_cond_chg LINES ld_lines.
 READ TABLE lt_cond_chg INTO ls_cond_chg_tmp INDEX ld_lines.
 IF sy-subrc EQ 0.
 ld_ajout_cond = abap_true.
 MOVE-CORRESPONDING ls_komv_print_src TO ls_cond_chg.
 ls_cond_chg-knumv = ls_cond_chg_tmp-knumv.
 ls_cond_chg-kposn = ls_cond_chg_tmp-kposn.
 ls_cond_chg-stunr = ls_cond_chg_tmp-stunr + 10.
 ELSE.
 CLEAR: ls_cond_chg, ld_lines, ls_komv_print_dest, ls_cond_chg_tmp.
 CONTINUE.
 ENDIF.
 ENDIF.
* Format décimal
 CASE gv_decimal.
 WHEN space. "format N.NNN,NN
 REPLACE ALL OCCURRENCES OF '.' IN ls_cond_chg-kbetr_prt WITH ','.
 WHEN 'Y'. "format N NNN NNN,NN
 REPLACE ALL OCCURRENCES OF '.' IN ls_cond_chg-kbetr_prt WITH ','.
 ENDCASE.
* Récupérer les nouvelles conditions qui seront ajouté au document destinataire
 IF ld_ajout_cond EQ abap_true.
 INSERT ls_cond_chg INTO TABLE lt_cond_chg_insert.
 ENDIF.
 INSERT ls_cond_chg INTO TABLE lt_cond_chg.
 CLEAR ls_cond_chg.
 ENDLOOP.
 CALL FUNCTION 'PRC_INT_ITEM_INPUT'
 EXPORTING
 iv_pd_handle = ld_pd_handle_dest
 iv_item_no = <fs_orderadm_i_dest>-guid
 it_cond_prt = lt_cond_chg
 iv_bal_log = bal_log
 iv_req_ret = abap_true
 iv_req_cond_prt = abap_true
 IMPORTING
 et_item_ret = lt_item_ret
 et_cond_prt = lt_cond_ret
 ev_data_changed = ld_data_changed
 EXCEPTIONS
 non_existing_handle = 1
 non_existing_item = 2
 ipc_error = 3.
 IF sy-subrc = 0.
* En cas d'ajout de nouvelles conditions de prix, appeler le MF PRC_INT_ITEM_INPUT
* avec les montants
 IF lt_cond_chg_insert IS NOT INITIAL.
 REFRESH lt_cond_chg[].
 lt_cond_chg[] = lt_cond_ret[].
 LOOP AT lt_cond_chg_insert ASSIGNING <fs_cond_chg_insert>.
 READ TABLE lt_cond_chg ASSIGNING <fs_cond_chg> WITH KEY kschl = <fs_cond_chg_insert>-kschl.
 IF sy-subrc EQ 0.
 <fs_cond_chg>-kwert = <fs_cond_chg_insert>-kwert.
 <fs_cond_chg>-kbetr_prt = <fs_cond_chg_insert>-kbetr_prt.
 ENDIF.
 ENDLOOP.
 REFRESH lt_cond_ret[].
 CALL FUNCTION 'PRC_INT_ITEM_INPUT'
 EXPORTING
 iv_pd_handle = ld_pd_handle_dest
 iv_item_no = <fs_orderadm_i_dest>-guid
 it_cond_prt = lt_cond_chg
 iv_bal_log = bal_log
 iv_req_ret = abap_true
 iv_req_cond_prt = abap_true
 IMPORTING
 et_item_ret = lt_item_ret
 et_cond_prt = lt_cond_ret
 ev_data_changed = ld_data_changed
 EXCEPTIONS
 non_existing_handle = 1
 non_existing_item = 2
 ipc_error = 3.
 ENDIF.
* Publish event afin de sauvegarder les conditions de prix
 CALL FUNCTION 'CRM_EVENT_PUBLISH_OW'
 EXPORTING
 iv_obj_name = 'PRIDOC'
 iv_guid_hi = pd_guid_dest
 iv_kind_hi = 'A'
 iv_event = 'SAVE'
 EXCEPTIONS
 OTHERS = 1.
* As no order_maintain will follow implicitly and therefore no
* exec times for the events will be set, call CRM_ORDER_MAINTAIN
* without any parameters
* Then the exec time 'end of document' will be set and with the
* group logic also all exec times before
* But at least one object is needed in input_fields
* --> use PRIDOC
 ls_input_fields-ref_guid = <fs_orderadm_i_dest>-guid.
 ls_input_fields-ref_kind = 'B'.
 ls_input_fields-objectname = 'PRIDOC'.
 INSERT ls_input_fields INTO TABLE lt_input_fields.
 CLEAR ls_input_fields.
 CALL FUNCTION 'CRM_ORDER_MAINTAIN'
 CHANGING
 ct_input_fields = lt_input_fields
 EXCEPTIONS
 error_occurred = 1
 document_locked = 2
 no_change_allowed = 3
 no_authority = 4
 OTHERS = 5.
 ENDIF.
ENDLOOP.
" F_MODIF_CONDITION_PRIX
*& Form F_LOCK_DOCUMENT
* Verrouillage d'un document
FORM f_lock_document USING pd_guid TYPE crmt_object_guid.
CONSTANTS : lc_orderadm_h TYPE crmt_object_name VALUE 'ORDERADM_H',
 lc_orderadm_i TYPE crmt_object_name VALUE 'ORDERADM_I'.
DATA: lv_process_mode TYPE crmt_mode,
 lv_order_initialized TYPE crmt_boolean,
 lv_process_type TYPE crmt_process_type,
 lv_already_locked TYPE abap_bool.
DATA: ls_admin_ui_status TYPE crmt_admin_ui_status,
 ls_item_usage_range TYPE crmt_item_usage_range.
DATA: lt_objects_to_read TYPE crmt_object_guid_tab,
 lt_requested_objects TYPE crmt_object_name_tab,
 lt_item_usage_range TYPE crmt_item_usage_range_tab,
 lt_locked_contract TYPE crmt_object_guid_tab.
INSERT pd_guid INTO TABLE lt_objects_to_read.
INSERT lc_orderadm_h INTO TABLE lt_requested_objects.
INSERT lc_orderadm_i INTO TABLE lt_requested_objects.
ls_item_usage_range-sign = 'E'.
ls_item_usage_range-value = '02'.
INSERT ls_item_usage_range INTO TABLE lt_item_usage_range.
* LAM: Financing Options should be viewed in a separate screen:
ls_item_usage_range-sign = 'E'.
ls_item_usage_range-value = '05'. "Financing options
INSERT ls_item_usage_range INTO TABLE lt_item_usage_range.
*-> read document in change mode
CALL FUNCTION 'CRM_ORDER_READ'
 EXPORTING
 it_header_guid = lt_objects_to_read
 iv_mode = 'B'
 it_requested_objects = lt_requested_objects
 it_item_usage_range = lt_item_usage_range
 EXCEPTIONS
 document_not_found = 1
 error_occurred = 2
 document_locked = 3
 no_change_authority = 4
 no_display_authority = 5
 OTHERS = 6.
PERFORM enqueue_order IN PROGRAM saplcrm_order_ow IF FOUND
 USING pd_guid
 abap_false
 abap_false
 abap_false
CHANGING sy-subrc
 lv_already_locked
 lt_locked_contract.
" F_LOCK_DOCUMENT
* Fin Ajout CD1K904074-001
FORM f_header_copy_pricing USING pd_guid_src
pd_guid_dest.
DATA : ld_pd_handle_src TYPE prct_handle,
 ld_pd_handle_dest TYPE prct_handle,
 lt_komv_print_src TYPE prct_cond_print_t,
lt_komv_print_dest TYPE prct_cond_print_t,
 ls_komv_print_dest LIKE LINE OF lt_komv_print_dest,
 ls_komv_print_src LIKE LINE OF lt_komv_print_src,
 lt_cond_chg TYPE prct_cond_print_t,
 ls_cond_chg TYPE prct_cond_print,
 ls_input_fields TYPE crmt_input_field,
 lt_input_fields TYPE crmt_input_field_tab.
DATA : bal_log TYPE balloghndl,
 lt_cond_ret TYPE prct_cond_print_t,
 ld_data_changed TYPE xfeld,
 gv_decimal TYPE usdefaults-dcpfm.
* Verrouillage des documents source et destinataire
PERFORM f_lock_document USING pd_guid_src.
PERFORM f_lock_document USING pd_guid_dest.
* Récupérer le pricing handle des documents
* Document source
CALL FUNCTION 'CRM_PRIDOC_GET_HANDLE_OW'
 EXPORTING
 iv_header_guid = pd_guid_src
 IMPORTING
 ev_pd_handle = ld_pd_handle_src
 EXCEPTIONS
 error_occurred = 1
 handle_determination_error = 2
 orgdata_error = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 RETURN.
ENDIF.
* Document destinataire
CALL FUNCTION 'CRM_PRIDOC_GET_HANDLE_OW'
 EXPORTING
 iv_header_guid = pd_guid_dest
 IMPORTING
 ev_pd_handle = ld_pd_handle_dest
 EXCEPTIONS
 error_occurred = 1
 handle_determination_error = 2
 orgdata_error = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 RETURN.
ENDIF.
* * Récupérer les pricing document
* Document Source
CALL FUNCTION 'PRC_PD_HEAD_SHOW'
 EXPORTING
 iv_pd_handle = ld_pd_handle_src
 IMPORTING
 et_komv_print = lt_komv_print_src
 EXCEPTIONS
 non_existing_handle = 1
 ipc_error = 2
 OTHERS = 3.
CHECK sy-subrc EQ 0.
* Document Destinataire
CALL FUNCTION 'PRC_PD_HEAD_SHOW'
 EXPORTING
 iv_pd_handle = ld_pd_handle_dest
 IMPORTING
et_komv_print = lt_komv_print_dest
 EXCEPTIONS
 non_existing_handle = 1
 ipc_error = 2
 OTHERS = 3.
CHECK sy-subrc EQ 0.
* * Modification et Suppression des conditions de prix
LOOP AT lt_komv_print_src INTO ls_komv_print_src .
 CLEAR: ls_cond_chg,
 ls_komv_print_dest.
 MOVE-CORRESPONDING ls_komv_print_src TO ls_cond_chg.
* Rechercher la condition sur le document source
 READ TABLE lt_komv_print_dest INTO ls_komv_print_dest WITH KEY kschl = ls_komv_print_src-kschl
zaehk = ls_komv_print_src-zaehk.
 IF sy-subrc EQ 0.
 IF ls_komv_print_src-kbetr NE ls_komv_print_dest-kbetr.
 ls_cond_chg-kbetr_prt = ls_komv_print_src-kbetr_prt.
 ls_cond_chg-kwert = ls_komv_print_src-kwert.
 ls_cond_chg-kinak = ls_komv_print_src-kinak.
 CASE gv_decimal.
 WHEN space. "format N.NNN,NN
 REPLACE ALL OCCURRENCES OF '.' IN ls_cond_chg-kbetr_prt WITH ','.
 WHEN 'Y'. "format N NNN NNN,NN
 REPLACE ALL OCCURRENCES OF '.' IN ls_cond_chg-kbetr_prt WITH ','.
 ENDCASE.
 ENDIF.
 ENDIF.
 CLEAR ls_cond_chg-krech.
 INSERT ls_cond_chg INTO TABLE lt_cond_chg.
 CLEAR ls_cond_chg.
ENDLOOP.
CALL FUNCTION 'PRC_INT_HEAD_INPUT'
 EXPORTING
 iv_pd_handle = ld_pd_handle_dest
 iv_bal_log = bal_log
 it_cond_prt = lt_cond_chg
 iv_req_ret = abap_true
 iv_req_cond_prt = abap_true
 IMPORTING
 et_cond_prt = lt_cond_ret
 ev_data_changed = ld_data_changed
 EXCEPTIONS
 non_existing_handle = 1
 ipc_error = 2
 not_allowed = 3
 OTHERS = 4.
CHECK sy-subrc EQ 0.
* * Publish event afin de sauvegarder les conditions de prix
CALL FUNCTION 'CRM_EVENT_PUBLISH_OW'
 EXPORTING
 iv_obj_name = 'PRIDOC'
 iv_guid_hi = pd_guid_dest
 iv_kind_hi = 'A'
 iv_event = 'SAVE'
 EXCEPTIONS
 OTHERS = 1.
* As no order_maintain will follow implicitly and therefore no
* exec times for the events will be set, call CRM_ORDER_MAINTAIN
* without any parameters
* Then the exec time 'end of document' will be set and with the
* group logic also all exec times before
* But at least one object is needed in input_fields
* --> use PRIDOC
ls_input_fields-ref_guid = pd_guid_dest.
ls_input_fields-ref_kind = 'A'.
ls_input_fields-objectname = 'PRIDOC'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
CLEAR ls_input_fields.
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
 CHANGING
 ct_input_fields = lt_input_fields
 EXCEPTIONS
 error_occurred = 1
 document_locked = 2
 no_change_allowed = 3
 no_authority = 4
 OTHERS = 5.
ENDFORM.
FORM f_header_copy_pricing USING pd_guid_src
pd_guid_dest.
DATA : ld_pd_handle_src TYPE prct_handle,
 ld_pd_handle_dest TYPE prct_handle,
 lt_komv_print_src TYPE prct_cond_print_t,
lt_komv_print_dest TYPE prct_cond_print_t,
 ls_komv_print_dest LIKE LINE OF lt_komv_print_dest,
 ls_komv_print_src LIKE LINE OF lt_komv_print_src,
 lt_cond_chg TYPE prct_cond_print_t,
 ls_cond_chg TYPE prct_cond_print,
 ls_input_fields TYPE crmt_input_field,
 lt_input_fields TYPE crmt_input_field_tab.
DATA : bal_log TYPE balloghndl,
 lt_cond_ret TYPE prct_cond_print_t,
 ld_data_changed TYPE xfeld,
 gv_decimal TYPE usdefaults-dcpfm.
PERFORM f_lock_document USING pd_guid_src.
PERFORM f_lock_document USING pd_guid_dest.
* Récupérer le pricing handle des documents
* Document source
CALL FUNCTION 'CRM_PRIDOC_GET_HANDLE_OW'
 EXPORTING
 iv_header_guid = pd_guid_src
 IMPORTING
 ev_pd_handle = ld_pd_handle_src
 EXCEPTIONS
 error_occurred = 1
 handle_determination_error = 2
 orgdata_error = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 RETURN.
ENDIF.
* Document destinataire
CALL FUNCTION 'CRM_PRIDOC_GET_HANDLE_OW'
 EXPORTING
 iv_header_guid = pd_guid_dest
 IMPORTING
 ev_pd_handle = ld_pd_handle_dest
 EXCEPTIONS
 error_occurred = 1
 handle_determination_error = 2
 orgdata_error = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 RETURN.
ENDIF.
* * Récupérer les pricing document
* Document Source
CALL FUNCTION 'PRC_PD_HEAD_SHOW'
 EXPORTING
 iv_pd_handle = ld_pd_handle_src
 IMPORTING
 et_komv_print = lt_komv_print_src
 EXCEPTIONS
 non_existing_handle = 1
 ipc_error = 2
 OTHERS = 3.
CHECK sy-subrc EQ 0.
* Document Destinataire
CALL FUNCTION 'PRC_PD_HEAD_SHOW'
 EXPORTING
 iv_pd_handle = ld_pd_handle_dest
 IMPORTING
et_komv_print = lt_komv_print_dest
 EXCEPTIONS
 non_existing_handle = 1
 ipc_error = 2
 OTHERS = 3.
CHECK sy-subrc EQ 0.
* * Modification et Suppression des conditions de prix
LOOP AT lt_komv_print_src INTO ls_komv_print_src .
 CLEAR: ls_cond_chg,
 ls_komv_print_dest.
 MOVE-CORRESPONDING ls_komv_print_src TO ls_cond_chg.
* Rechercher la condition sur le document source
 READ TABLE lt_komv_print_dest INTO ls_komv_print_dest WITH KEY kschl = ls_komv_print_src-kschl
zaehk = ls_komv_print_src-zaehk.
 IF sy-subrc EQ 0.
 IF ls_komv_print_src-kbetr NE ls_komv_print_dest-kbetr.
 ls_cond_chg-kbetr_prt = ls_komv_print_src-kbetr_prt.
 ls_cond_chg-kwert = ls_komv_print_src-kwert.
 ls_cond_chg-kinak = ls_komv_print_src-kinak.
 CASE gv_decimal.
 WHEN space. "format N.NNN,NN
 REPLACE ALL OCCURRENCES OF '.' IN ls_cond_chg-kbetr_prt WITH ','.
 WHEN 'Y'. "format N NNN NNN,NN
 REPLACE ALL OCCURRENCES OF '.' IN ls_cond_chg-kbetr_prt WITH ','.
 ENDCASE.
 ENDIF.
 ENDIF.
 CLEAR ls_cond_chg-krech.
 INSERT ls_cond_chg INTO TABLE lt_cond_chg.
 CLEAR ls_cond_chg.
ENDLOOP.
CALL FUNCTION 'PRC_INT_HEAD_INPUT'
 EXPORTING
 iv_pd_handle = ld_pd_handle_dest
 iv_bal_log = bal_log
 it_cond_prt = lt_cond_chg
 iv_req_ret = abap_true
 iv_req_cond_prt = abap_true
 IMPORTING
 et_cond_prt = lt_cond_ret
 ev_data_changed = ld_data_changed
 EXCEPTIONS
 non_existing_handle = 1
 ipc_error = 2
 not_allowed = 3
 OTHERS = 4.
CHECK sy-subrc EQ 0.
CALL FUNCTION 'CRM_EVENT_PUBLISH_OW'
 EXPORTING
 iv_obj_name = 'PRIDOC'
 iv_guid_hi = pd_guid_dest
 iv_kind_hi = 'A'
 iv_event = 'SAVE'
 EXCEPTIONS
 OTHERS = 1.
ls_input_fields-ref_guid = pd_guid_dest.
ls_input_fields-ref_kind = 'A'.
ls_input_fields-objectname = 'PRIDOC'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
CLEAR ls_input_fields.
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
 CHANGING
 ct_input_fields = lt_input_fields
 EXCEPTIONS
 error_occurred = 1
 document_locked = 2
 no_change_allowed = 3
 no_authority = 4
 OTHERS = 5.

Pricing conditions changed should get approval

Similar Messages

Maybe you are looking for