Conditions not updated in Contract Creation using BAPI_CONTRACT_CREATE

Hi all,
The conditions for the Contracts does not get updated eventhough the contract is created.
   BAPI Used : BAPI_CONTRACT_CREATE
iam using the following code,
conitem_cond_validity-item_no      = con_data-ebelp.
conitem_cond_validity-plant        = con_data-werks.
CONCATENATE con_headerdata-kdatb6(4) con_headerdata-kdatb3(2) con_headerdata-kdatb+0(2)
INTO conitem_cond_validity-valid_from.
CONCATENATE con_headerdata-kdate6(4) con_headerdata-kdate3(2) con_headerdata-kdate+0(2)
INTO conitem_cond_validity-valid_to.
APPEND conitem_cond_validity.
CLEAR conitem_cond_validity.
   the respective conitem_cond_validityx table has been updated with the value 'X'.
   conitem_condition-item_no    = con_data-ebelp.
   conitem_condition-cond_type     = kschl_1.
   conitem_condition-cond_value    = kbetr_1.
   conitem_condition-currency      = konwa_1.
   conitem_condition-cond_unit     = kmein_1.
    conitem_condition-cond_p_unt    = kpein_1.
   conitem_condition-numerator    = kumza_1.
   conitem_condition-denominator    = kumne_1.
   conitem_condition-change_id     = 'I'.
   APPEND conitem_condition.
   CLEAR conitem_condition.
   the respective conitem_conditionx table has been updated with the value 'X'.
   Please help to solve the issue.
Thanks and Regards,
Raj

Hi Paromita Roy Chowdhury,
without knowing your exact situation (code), i can see a possible reasons: If it is exactly the 1000th, there may be a field of length 3 used as counter that will overflow when adding 1 to 999.
Regards,
Clemens

Similar Messages

Planner group is not updated in service notification using BAPI

Hi,
Planner group is not updated in service notification using BAPI BAPI_ALM_ORDER_MAINTAIN.
I have written the below code, but planner group is not updated in the service notification.
Please advice which parameters do i need to pass to update planner group in the service notification.
          wa_methods-refnumber      = '000001'.
          wa_methods-objecttype     = 'PARTNER'.
          wa_methods-method         = 'CREATE'.
          wa_methods-objectkey      = wa_subscr1-aufnr.
          APPEND wa_methods TO i_methods.
          wa_methods-refnumber      = '000002'.
          wa_methods-objecttype     = 'HEADER'.
          wa_methods-method         = 'CREATE'.
          wa_methods-objectkey      = wa_subscr1-aufnr.
          APPEND wa_methods TO i_methods.
          wa_methods-refnumber      = '000000'.
          wa_methods-objecttype     = ' '.
          wa_methods-method         = 'SAVE'.
          APPEND wa_methods TO i_methods.
          REFRESH i_partner.
          CLEAR wa_partner.
          wa_partner-orderid        = wa_subscr1-aufnr.
          wa_partner-partn_role     = 'VW'.
          wa_partner-partn_role_old = ''.
          wa_partner-partner        = wa_subscr1-parnr.
          wa_partner-partner_old    = ''.
          APPEND wa_partner TO i_partner.
          REFRESH i_planrgrp.
          CLEAR wa_planrgrp.
          wa_planrgrp-orderid        = wa_subscr1-aufnr.
          wa_planrgrp-plangroup      = wa_subscr1-ingpr.
          APPEND wa_planrgrp TO i_planrgrp.
          REFRESH i_planrgrp_up.
          CLEAR wa_planrgrp_up.
          wa_planrgrp_up-orderid     = wa_subscr1-aufnr.
          wa_planrgrp_up-plangroup   = 'X'.
          APPEND wa_planrgrp_up TO i_planrgrp_up.
*----Change order details with Technician name
          CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
            TABLES
              it_methods   = i_methods
              it_header    = i_planrgrp
            it_header_up = i_planrgrp_up
              it_partner   = i_partner
              return       = i_return.
Thanks & regards,
Krishna

Try this way
CALL FUNCTION 'BAPI_SERVNOT_CREATE'
EXPORTING
* EXTERNAL_NUMBER =
notif_type = 'S3'
notifheader = ls_notif_h
* TASK_DETERMINATION = ' '
* SENDER =
* ORDERID =
IMPORTING
NOTIFHEADER_EXPORT = ls_notif_e
TABLES
* NOTITEM =
* NOTIFCAUS =
* NOTIFACTV =
* NOTIFTASK =
* NOTIFPARTNR =
* LONGTEXTS =
* KEY_RELATIONSHIPS =
return = lt_return
* IF lt_return IS INITIAL.                                               " <<< Comment this lie
read table lt_return into ls_return with key type = 'E'. " << Change
if sy-subrc ne 0.                                                             " << Change
COMMIT WORK AND WAIT.
write: / ls_notif_e-NOTIF_NO.
ELSE.
LOOP AT lt_return INTO ls_return.
WRITE:/ 'errors'.
* ls_return.
ENDLOOP.
endif.
a®

HT6147 Why haven't they done a patch for those of us who have not updated and prefer to use iOS 6?

Why haven't they done a patch for those of us who have not updated and prefer to use iOS 6?

Totally agree with Andy. Apple needs to support its users whether or not they decide to update to iOS 7.
The reviews from i Pad 3 owners (like me) is that when they've updated to iOS 7 they've experienced latency and sluggishness. Why would I ruin a perfectly good iPad by updating to iOS 7?
Please let me know where I can find a patch for iOS 6.
Thanks!

Configuration is not updating in sales order using function module SD_SALESDOCUMENT_CREATE

Hello Experts,
we are using SD_SALESDOCUMENT_CREATE function module to create sales order.
Sales order is creating successfully but the configuration for the items are not updating.
Could any one help me out on this ....we tried in different ways but couldn't ....
Here is the code....
*---Filling Configuration data
*--- Filling Configuration Reference Item / Instance
     w_sales_cfgs_refinst-posex     = w_items-itm_number.
     w_sales_cfgs_refinst-config_id = '000001'.
     w_sales_cfgs_refinst-inst_id   = '00000001'.
     APPEND w_sales_cfgs_refinst TO t_sales_cfgs_refinst.
     CLEAR w_sales_cfgs_refinst.
*---Filling Configuration Reference Data SALES_CFGS_REF Table
     w_sales_cfgs_ref-posex      = w_items-itm_number.
     w_sales_cfgs_ref-config_id = '000001'.
     w_sales_cfgs_ref-sce        = '1'.
     w_sales_cfgs_ref-root_id    = '00000001'.
     w_sales_cfgs_ref-complete   = 'T'.
     w_sales_cfgs_ref-consistent = 'T'.
     APPEND w_sales_cfgs_ref TO t_sales_cfgs_ref.
     CLEAR w_sales_cfgs_ref.
*---Filling Configuration Instances SALES_CFGS_INST Table
     w_sales_cfgs_inst-config_id       = '000001'.
     w_sales_cfgs_inst-inst_id         = '00000001'.
     w_sales_cfgs_inst-obj_type        = 'MARA'.
     w_sales_cfgs_inst-class_type      = '001'.
     w_sales_cfgs_inst-obj_key         = w_sales_items_in-material.
     w_sales_cfgs_inst-quantity        = w_items-target_qty.
     w_sales_cfgs_inst-quantity_unit   = 'EA'.
     w_sales_cfgs_inst-complete        = 'T'.
     w_sales_cfgs_inst-consistent      = 'T'.
     w_sales_cfgs_inst-OBJECT_GUID     = 'T'.
     w_sales_cfgs_inst-PERSIST_ID_TYPE = w_sales_items_in-material.
     APPEND w_sales_cfgs_inst TO t_sales_cfgs_inst.
     CLEAR w_sales_cfgs_inst.
*---Filling Configuration Characteristic Values SALES_CFGS_VALUE Table
     LOOP AT w_items-itm_config INTO wa_itm_config.
       w_sales_cfgs_value_in-config_id = '000001'.
       w_sales_cfgs_value_in-inst_id   = '00000001'.
       w_sales_cfgs_value_in-charc     = wa_itm_config-charc_name.
       w_sales_cfgs_value_in-value     = wa_itm_config-charc_value.
       APPEND w_sales_cfgs_value_in TO t_sales_cfgs_value.
*---Filling Configuration Variant Condition Key SALES_CFGS_VK
       w_sales_cfgs_vk-config_id = '000001'.
       w_sales_cfgs_vk-inst_id   = '00000001'.
       w_sales_cfgs_vk-vkey      = wa_itm_config-charc_name.
       APPEND w_sales_cfgs_vk TO t_sales_cfgs_vk.
       CLEAR : w_sales_cfgs_value_in,w_sales_cfgs_vk.
     ENDLOOP.
Regards,
Harsha P

Hello All,
Actually there was a bug in my code to update configuration for an item in sales order
Below is my Updated Code with that i can updated configuration successfully....
*---Filling Configuration data
*---Filling Configuration Reference Data SALES_CFGS_REF Table
     w_sales_cfgs_ref-posex      = w_items-itm_number.
     w_sales_cfgs_ref-config_id = '000001'.
     w_sales_cfgs_ref-sce        = '1'.
     w_sales_cfgs_ref-root_id    = '00000001'.
     w_sales_cfgs_ref-complete   = 'T'.
     w_sales_cfgs_ref-consistent = 'T'.
     APPEND w_sales_cfgs_ref TO t_sales_cfgs_ref.
     CLEAR w_sales_cfgs_ref.
*---Filling Configuration Instances SALES_CFGS_INST Table
     w_sales_cfgs_inst-config_id       = '000001'.
     w_sales_cfgs_inst-inst_id         = '00000001'.
     w_sales_cfgs_inst-obj_type        = 'MARA'.
     w_sales_cfgs_inst-class_type      = '300'.
     w_sales_cfgs_inst-obj_key         = w_sales_items_in-material.
     w_sales_cfgs_inst-quantity        = w_items-target_qty.
     w_sales_cfgs_inst-quantity_unit   = 'EA'.
     w_sales_cfgs_inst-complete        = 'T'.
     w_sales_cfgs_inst-consistent      = 'T'.
     w_sales_cfgs_inst-object_guid     = w_sales_items_in-material.
     w_sales_cfgs_inst-persist_id_type = 'G'.
     APPEND w_sales_cfgs_inst TO t_sales_cfgs_inst.
     CLEAR w_sales_cfgs_inst.
*---Filling Configuration Characteristic Values SALES_CFGS_VALUE Table
     LOOP AT w_items-itm_config INTO wa_itm_config.
       w_sales_cfgs_value_in-config_id = '000001'.
       w_sales_cfgs_value_in-inst_id   = '00000001'.
       w_sales_cfgs_value_in-charc     = wa_itm_config-charc_name.
       w_sales_cfgs_value_in-value     = wa_itm_config-charc_value.
       APPEND w_sales_cfgs_value_in TO t_sales_cfgs_value.
*---Filling Configuration Variant Condition Key SALES_CFGS_VK
       w_sales_cfgs_vk-config_id = '000001'.
       w_sales_cfgs_vk-inst_id   = '00000001'.
       w_sales_cfgs_vk-vkey      = wa_itm_config-charc_name.
       APPEND w_sales_cfgs_vk TO t_sales_cfgs_vk.
       CLEAR : w_sales_cfgs_value_in,w_sales_cfgs_vk.
     ENDLOOP.
     CLEAR : w_sales_items_in,wa_mara,w_items,w_sales_schedules_in,
             w_items-itm_number.
   ENDLOOP.
Cheers,
Harsha

M/08 maintain pricing condition not updating

Hi experts ,
I have written some code in one of the form in M/08 transaction for accomodating changes in the Pricing schema of PO .I have checkde the Statistics checkbox for that form .
I have used the form for VAT calculation using Excise Duty , E.cess and Sec.E.Cess and the i m getting the required values in the code part .
But the problem is that , its not updating the VAT value in the ME23N transaction in the Condition Item Tab .
Cond Tyope Statistics Subtot Condition Formula
247 0 ZTAX VAT Value X F 955
Please Suggest wat i need to do .!!
Regards Rajesh .

hi
good
if you are trying to update the pricing condition using the BDC recording then it may happen sometime that some your recording screens wont work proplerly in the production server so it wont take the appropriate data from the flat file.
Please debug the code in producation to point out the field which is not working properly than you do the recording again .
Hope this will help you to solve y our problem.
Thanks
mrutyun^

MWST condition type missing in contract creation,VA41

Hi, got a problem here during contract creation. I can't get the MWST show up in the contract condition tab. Analysis result :
010 Access not made (requirement not fulfilled)
Error Message : Pricing error: Mandatory condition MWST is missing
Things I have done :
a) checked pricing procedure V/08
b) created condition records VK11
c) checked customer tax classification : Liable for taxes
d) checked material tax data : Full tax
e) ???
what else did I miss out?
Thanks
Andy

Option 1: If you do not want MWST condition as mandatory, then remove the check from check box in the pricing procedure (T.Code: V/08). MWST is tax condition & Tax condition are normally not mandatory, as it may vary according to Business Requirement.
Option 2: <b>"010 Access not made (requirement not fulfilled)"</b>: Check the access sequence maintained for Condition Type MWST (T.Code": V/06). Next, Check the Access Sequence & the access 010 assigned to it. (T.Code:V/07). Check whether Accesses & fields are assigned correctly.
Option 3: Instead of maintaining condition record for access 010, maintain for different combination & check the result. Even in my case, once the access with reference to tax classification did not give desired result, but was achieved bu maintaining another combination.
Regards,
Rajesh Banka
Reward points if helpful.

Commitment is not updated after PO creation !

After creation of a PO referenced to a PR created from MD51 on a WBS, the commitment in "S_ALR_87013533 - Plan/Actual/Commitment/Rem.Plan/Assigned " is not updated although i believe that all configs are done. any one faced this prob.?

There is this note (47992 - No commitment is displayed in reporting) which explains when Commitments would not be generated. Please check if you case belongs to any of these:
1. For purchase orders/ purchase requisitions for project stock or customer stock with settlement on the project or sales order, no commitment is written in the standard program in general. If you want a commitment being written in these cases as well, apply the corrections from Note 498907
2. If a purchase requisition which is assigned to a WBS element is generated from material requirements planning (MRP), no commitment is generated for the WBS element.
Note also explains how updation of commitment values is controlled:
1. In the year-dependent controlling area control parameters, commitments management must be active (Transaction OKKP).
2. In addition, the G/L account to which the purchase order is assigned, must be created as a cost element at the delivery date.
Regeneration of the commitment afterwards is possible by changing the purchasing document (for example, the item text).
Regards
Sreenivas

Credit Exposure have not updated after SO creation

Hi Expert,
As per business requirement, we want to maintained credit check during consignment process. Here we have unable to stop Consignment Fill-up order with excess credit limit.
EX: In FD32, Customer Credit Limit: 100000
If we create first Consignment Fill-up order with amount 90000 and create second order with amount 15000 than system is allowing to create SO and in FD32, Credit exposure amount not updated in both cases.
I have also active credit limit with item category. Please find the our current setting in VOV8 and OVA8.
Please suggest how can we configure this process.
Thanks in advance.
Regards,
Shatrughan Singh

Even though you activated the credit active to KBN still system will not update those values to FD32.
This is standard behavior of SAP R/3 system, please see the note SAP 492831 which clearly says credit management for consignment works for consignment issue.Not in Consignment fill up.
I am assuming that the reason could be the consignment fill up does not update the open order values to FD32 is
Since the consignment fill up is just dumping the stock at customer location, let us assume if the goods are not sold by the customer to end customer then again we need to get those items back to our ware house so here there is no point of updating the credit values to customer in to FD32
And it is not relevant for billing hence there is no point of talking about credit block
thanks,
Srinu.

Discount value not updating at contract header level

Dear Friends
I am facing problem of updating discount value at contract header level. The scenario is u2026. my client used to provide certain service to their customer. For that they maintain quantity contract & bill them as per billing plan. When customer avail three or more services they get 10% extra discount. Now the problem is after continue for some days if some customer wants to drop one item we are cancelling the line item by assigning proper cancellation procedure but the system is not reversing the 10% discount.
Example u2013
Contract valid for 1st Jan 2009 to 31st Dec 2010(Value for each service = 10)
(Total no of item-3)
(Discount-10%)
Here bill value for each month is 10x3-(30x0.10) =27
At the month of march 2009 customer decided to drop for one item so hence forth the bill value should be 10x2=20
But the system is calculating 10x2-(20x0.10)=18
We need to update the value at contract header level only to satisfy some CRM functionality.
Please suggest how to solve this issue

Hi,
If that is item condition then you can not change it at header level
check in M/06 make it at header level in change which can be made tab
Regards
Kailas Ugale

Contract creation using BDC wherein Net order price is Zero

Hi,
Please let me know the solution to the above problem.
I am trying to create a quantity contract using BDC but the Net Order Price is coming as Zero even though the condition type PB00 is maintained properly in the info record with some net order price which is not equal to zero.
Please let me know asap as this is a critical issue. The same problem is not happening if i try an create a contract manually.

Hi,
Please let me know the solution to the above problem.
I am trying to create a quantity contract using BDC but the Net Order Price is coming as Zero even though the condition type PB00 is maintained properly in the info record with some net order price which is not equal to zero.
Please let me know asap as this is a critical issue. The same problem is not happening if i try an create a contract manually.

Pricing condition not updating

Hi All,
When using 'BAPI_BUSPROCESSND_CREATEMULTI' , I am able to create header and items but I am not able to create pricing conditions ( in table PRCD_COND).
Can any one please help me how to solve this issue?

Hi,
Use BAPI: BAPI_SALESORDER_CHANGE to update the data.
BAPI_SALESORDER_CREATEFROMDAT2 is used to create new Sales orders.
Regards,
Tim

Batch not updating while creating delivery using bapi

Hi
I have used following bapi to create delivery BAPI_DELIVERYPROCESSING_EXEC and passed the following parameters into bapi
lt_request-document_type = 'A'.
        lt_request-document_numb = deltab-vbeln.
        lt_request-document_item = deltab-posnr.
        lt_request-batch        = deltab-charg.
        lt_request-material = deltab-matnr.
        lt_request-plant = '3200'.
        lt_request-quantity_base__uom = deltab-kwmeng.
        lt_request-delivery_date = sy-datum.
CALL FUNCTION 'BAPI_DELIVERYPROCESSING_EXEC'
EXPORTING
DELIVERY_EXTEND =
TECHN_CONTROL =
      TABLES
      request = lt_request
      createditems = lt_createditems
      return = lt_return.
here i am able to create delivery successfully but the batch which i passed in bapi is not getting updated in vl02n to do PGI.
again i need to go to vl02n and give batch and quanitty manually to do PGI.is there anyway that batch gets updated in vl02n also.
Regards,
Venkat.

Hi
My answer is pure assumption.
Please check the following OSS notes
Note 758810 - BAPI_PO_CHANGE vendor batch and batch not visible
Note 1230268 - Field Vendor Batch never filled for PO BAPIs
Please take help from BASIS and SAP, before implementing the OSS note
Regards
Madhan D

Active Directory cn field not updated from sap HR using ldap.

Hi,
Apologies if this is in the wrong forum area.
I am using the LDAP facility to create and modify Active Directory records from sap HR. Initially, the name field cn that was coming across into AD was in the format of the logical system and employee number, eg, RD4CLNT22000000711.
I then implemented the BADI HRLDAP_ATTRIBUTES which then changed this name field cn in the active directory listing to the format; surname, forename.
It works fine when I create a new user, however the problem comes when I update the persons name in the sap hr module. The data that comes across into Active Directory shows the change to the persons surname sn, forename and displayname fields is there but the cn field is still showing as the previous name.
In short, when a new user is created, the cn field in active directory is correct
(surname, forename) but when the employees name is modified, that change is not brought across to the cn field even though the surname, forename and displayname fields are updated correctlyon AD.
We are on release 4.70.
Anyway, if anyone could help I would be very grateful.
Thanks
David

Hi
The problem it is causing us is that the cn field is incorrect and does not mirror the change in sap HR, therefore the Active Directory entry for the employee is not totally accurate.
When an employee changes their name in SAP HR - usually their surname, we would then want to update the employees active directory account to show this change and this includes the cn field also. At the moment the firstname, lastname fields do get updated with the change so we would want the cn field to show this as well otherwise the cn field would be incorrect and not match up with the employee's AD firstname & lastname fields.
Dave

Issues during Contract creation using Inbound IDOC BLAORD03

Dear Experts,
We need to create Contract using Inbound IDOC BLAORD03.
I am facing following issues and need some one's help ASAP.
(1) Contract is generated without Header Texts and Item Texts through IDOC BLAORD03 .
(2) Not able to create CONTRACT for service masters using Inbound IDOC BLAORD03.
Is there any body who has implemented this scenario and able to guide ?
Looking forward to help ASAP.
Thanks in Advance,
Best Regards,
Mitesh Desai
[email protected]

Hi All,
I am also facing the same issue. I am trying to upload service outline agreements thru LSMW using idoc basiv type BLAORD03 ( FM->IDOC_INPUT_BLAORD).
Immediate help highly appreciated.
Thanks & Regards,
Vijender

Thesaurus not updating on all servers using workbench

When I update the thesaurus using the Workbench, only 2 out of 3 of our servers get updated. I checked the AppConfig.xml and all 3 servers are set up in the Dgraph cluster.
I found this error in the shell logs on the server that failed to update:
/bin/sh: emgr_update: command not found
Is that related to this issue? Are there other logs I should be checking for this?

From the error message, I think that the ENDECA_ROOT environment variable is not set on the MDEX server in question. The emgr_update utility is located inside $ENDECA_ROOT\bin (or %ENDECA_ROOT%\bin on Windows) so this would seem to make sense with your error message. You should be able to set it, export it and re-run. Note that you'll want to make the setting of this environment variable "persistent" by placing the commands in init.d or something similar, depending on how your organization runs your Linux servers.
Also, I agree with Frank, this should really be in the other forum as I imagine others will run into this issue from time to time. If this works, please "cross-post" over there.

Conditions not updated in Contract Creation using BAPI_CONTRACT_CREATE

Similar Messages

Maybe you are looking for