Condition Inactive

Hi,
In sales order all conditions are active (green), but in invoice all have become inactive.
Only list price is of manually entry, rest are from conditon records.
In copy control pricing type given as "D"
In case of this invoice the excise posting has been done but the commercial posting is not happening due to net value is zero becoz of inactive conditions
Regd

Hi
Kindly check Basic Pricing conditio type is assigned to pricing determination procedure at OVKK.
also check out a/c key is assigned to condition type in V/08.
at OVTP check ur Billing type is assigned to DuPP.
and also check the billing relevency whether it is oreder related or delivery related and accordingly cross check pricing type at copy control level..
thanks
Mahesh

Similar Messages

What does 'condition inactive' mean? Thanks in advance!

Hi, This question has puzzled me many days, but still no answer. Any one can help me ? Many many thanks!!
In SAP GUI, under item conditions tab, there is a column 'Exception' with traffic lights.
Three kinds of tracffic lights are avaible in this column, red, green, and Amber Light.
The explantion of F1 help is not so clearly. My questiones are:
1. If a condition type is with 'amber light', what does that mean?
2. If a condition type is with 'green light', what does that mean?
3. If a condition type is with 'red light', what does that mean?
4. If a condition type is inactive, How can I know why this condition type is 'inactive'?
Thanks soooooo much!!
Regards,
Hedy
Edited by: hedyee on Jul 25, 2009 12:06 PM

Hi,
Condition inactive means, condition is not active in that particular transaction.
The meaning for traffic lights is
Red: Condition Contains errors, which has to be rectified before saving.
Green: Condition is active in the transaction and the prices are taken into consideration.
Amber: Condition is inactive on various reasons (for e.g., due to subsequent price)
If a condition is inactive, the tool tip in Web UI shows the reason. But in SAP GUI, We need to go through the pricing procedure.
Regards,
Krishna

Condition inactive while making proforma invoice

Hi All,
when I am making a performa invoice for replenishment delivery for Stock transport order the pricing condition I am using is coming inactive with indicator "Inactive via formulae of incorrect".
Please help ASAP as we are at critical stage in the project.
Regards,
Puneet Makkar

Hi Dinesh,
yes it is a domestic document .. and it is non spesific for any location or material.. its just when i create a performa invoice from delivery type NL .. actually wht i got to know while debugging that it is not picking the document currency .. can u please daignose any valid reason of this.
Please help ASAP.
Regards,
Puneet Makkar

Condition Inactive because of subsequent price.

Hi All,
During Sales Order Processing in pricing only the last condition is actived & get reflected in net price. All other conditions are shown inactive. When I check the Item-Conditon-Details on the Control Data (Inactive Field) the status is shown Y- Inactive because of subsequent price.
We have created variant confugiration for the material.
Can anyone guide me where I have made the mistake.
Thanks is advance

hi,
i dont think it is really a mistake when the system says a condition is inactive because of a subsequent one. Like for example in a sales order there is a PR00 list price and some discount conditions on it.
But the moment we supply the sales order with a Net price (PN00 condition type)value we dont the discounts also to go along with that. because net price is after considering everything. In such case the discount conditions become inactive because of a subsequent price.
In your case please check your pricing procedure if it has purposefully been configured that way.
regards
sadhu kishore

Inactive condition type

Dear All
We have come across a situation where there were few EDI orders which came in and in those orders some of the line items had all its conditions inactive. That is List price, Taxes and customer price all are in yellow status ie. they are inactive.
As only few of the line items are inactive I am wondering what can be the reason for this behaviour.
If any one has any idea on the same then pls let me know
Many Thanks
Gauravl

Dear Friend,
Go to the configuration of the individual condition type, There should be only one condition type having function of Price and quantity. Observe the all and try to change the settting of the "condition class" and "condition type".
Hope issue will be resolved.
Regards,

Implement pricing conditions GAU1 and GAU2

Dear All,
I want to implement pricing procedure for precious metals.
Anyone who has implemeneted the procedure at their end please guide me towards the same .
In PO I am getting following error in condition type GAU1 Inactive status as "X" and message as " Inactive via formulae of incorrect "
Please help
Thanks
Garima

Actually i haven't worked on metal prices...but once i had faced same type of error in my freight condition types...SAP responded with some solutions which i am posting...please see whether these are useful or not:
(1) Condition row is inactive
The condition type (group condition or item condition) is listed with or without a pricing result in the condition row on the condition screen for the subitem. However, the condition value is ignored. On the condition details screen (double-click on the condition row), an indicator is set for 'Inactive'.
(1.1) Inactive indicator 'A condition exclusion item'
You have selected an exclusion procedure at subitem level for your freight cost price determination schema. The condition type with inactive status 'A' was excluded using this procedure in favor of another condition type (set as inactive).
Check: In favor of which condition type or condition exclusion group was the condition type in question excluded?
=> Use Customizing transaction T_32 to determine the condition exclusion group to which the relevant condition type was assigned and use Customizing transaction TOK8 to determine the exclusion procedure assigned to the price determination schema.
(1.2) 'K - Inactive due to calculation basis/shipping material type'
An automatically determined or manually created condition type is set as inactive (inactive indicator 'K'), even though a valid condition record was found according to the analysis.
Check 1: Do all handling units in the subitems belong to a 'material group for packaging materials' that is assigned to this particular packaging material type in Customizing? The calculation base of the condition type refers to handling units (calculation bases C, E or F) and, in Customizing (transaction T_06), a packaging material type (synonym: shipping material type field T685A-VHART) was specified for the condition type?
=> Material numbers are assigned to 'material groups for packaging materials' in the material master (transaction MM02). 'Material groups for packaging materials' are assigned to packaging material types in Customizing: Transaction VHZU or IMG -> Logistics General -> Handling Unit Management -> Basics -> Define Allowed Packaging Materials
Check 2: Was a valid condition record for this condition type found in all subitems for the calculation base used?
=> Extend the condition pricing data (transaction TK11) so that valid condition records can be found for all subitems. If necessary, use a price 0.
Check 3: Was the condition type only created manually for individual subitems?
=> Usually, manual conditions must be created for the calculation base in all subitems, with the value 0 if necessary. If changes were also permitted at header level for an item condition (in Customizing transaction T_06), you can automatically create identical entries in all subitems of the calculation base by creating the condition at header level. You can then adjust these templates (with the value 0 if required) at subitem level.
Notes: For background information and options for 'Inactive K', see also note 318775. For the system response in the case of manual changes to freight conditions, see consulting note 773038.
(1.3) Inactive 'L - Condition exclusion header or inactive at header level'
The condition type could not be evaluated as a group condition or was excluded as part of a header exclusion because of another condition type.
Check 1: Could the condition group be evaluated at all?
=> On the condition screen of the header conditions (enter '=kkon' in the command field), check whether different subgroups have been created for the condition type. If this is the case, several condition rows will be displayed for the same condition type. Also check the Check the scale input values in the individual condition display (double-click on the condition row).
Since neither the price determination analysis nor the condition record display is available at header level, you must check the price table for the condition type using a subitem: Is there also a valid scale level for each scale input value? The lowest scale level is often missing in from-scales and the highest conceivable scale level is often missing in to-scales. For example, a to-scale of 'to 30 TO' cannot evaluate any shipments with 31 tons. You therefore need to extend this scale to 'to 99999 TO'.
Check 2: Did you select an exclusion procedure for your freight cost price determination schema at header level?
=> Use Customizing transaction TOK8 to check whether the indicator 'A - header exclusion' was entered in the relevant column for the exclusion procedure that is assigned to the price determination schema. If this is the case, the group condition inactive status 'L' may have been excluded in favor of another group condition type using this exclusion (set as inactive).
Use Customizing transaction T_32 to determine the condition exclusion group to which the condition type in question was assigned and use Customizing transaction TOK8 to determine the condition type or condition exclusion group in favor of which the group condition type in question could have been excluded.
Check 3: Are you using your own scale or condition formula for a multi-dimensional group condition?
=> You may try to analyze the import parameter KOMK or KOMP for a group condition in this formula. However, these parameters are not filled in group processing: '...The components komk and komp are initial during processing of group conditions...' ('i - Formulas' button on the 'Scales for Conditions' detailed screen in Customizing transaction T_06).
The inactive indicator KINAK is set by default to 'T' for group processing (inactive at header level) and is converted to the more general 'L' by the subsequent price determination.
(1.4) 'X - Inactive via formulae or incorrect'
If an error occurs during processing of multi-dimensional conditions (for example, during conversion to scale units or in a customer-specific formulas for scale bases), the condition is usually set to inactive status 'X'.
Check: Are all formulas used in connection with this condition (condition base formula, scale base formula, condition value formula) error-free?
(1.5) 'Y - Inactive because of subsequent price'
According to the price determination logic in SD, there can only ever be one valid price in a pricing procedure. All other conditions are surcharges or discounts in some shape or form. Accordingly, the last, valid pricing condition (valid condition record and not equal to zero) always applies. All pricing conditions in the schema with a lower level number are set to inactive status 'Y inactive because of subsequent price'.
Check: If the required pricing condition was unintentionally set to inactive status 'Y' by a subsequent pricing condition, you must decide (using an exclusion procedure, if required) which of the pricing conditions is varied. All pricing conditions with inactive indicator 'Y' are included in the exclusion procedure.
Regards,
Indranil

Price (Catalog) COND_INACTIVE

Hi,
In the purchase order change version, i can see the above above subject message i.e Price (Catalog) COND_INACTIVE (Check box ticked)
How to make Catalog price condition Inactive.
I am getting below error while changing purchase order :in application monitor
PurchOrder xxxxxxxxx: Purchase order still contains faulty items
02.06.2009 14:17: 16 PurchOrder 6500031274: Net price must be greater than 0 (Zero)
Is this because of above setting?
Thanks,
Jai

Hi jai
SAP Note 973952 - Meaningful error messages not shown in
Application monitors
SAP Note 966323 - Service Item: Not able to create PO in
ERP backend
PO created with status : Transfer Failed (E.Sys.)
ECS describe requirement not transferred to backend
Transfer PO from SRM to R/3 - Error in Process
Problem with BAPI_PO_CREATE1
Error in transmission
Problem in creation of PO
STO classic scenario SRM 4.0
plz update which sap version? threre many threads discussion.
what is the history of sc /po details- what type of cart it was? look out all discussions.
so your po did not create in r/3 so far?
br
muthu

BAPI CHANGEMULTI and CRM_ORDER_MAINTAIN

Hi all,
I have a couple of questions which are strictly connected:
1. Does anybody know if BAPI BAPI_BUSPROCESSND_CHANGEMULTI, in CRM application is suitable for adding a new item in a sales order already created?
The fact we have set up parameter A (CREATE), in the internal table ITEM , but after a long debuggins Bapi return us the parameter A (MODIFY).
CALL FUNCTION 'BAPI_BUSPROCESSND_CHANGEMULTI'
TABLES
 HEADER = CT_ORDERADM_H
 ITEM = CT_ORDERADM_I
 SALES = it_sales
 ORGANISATION = it_organiz
 PRICING = it_pricing
 APPOINTMENT = it_appointment
 TEXT = it_text
 INPUT_FIELDS = ct_input
 RETURN = it_return_bapi
 CONDITION_CREATE = it_preciopos
 SCHEDULELINE = it_repartos
 BILLING = it_billing_maintain.
LOOP AT it_return_bapi.
 IF it_return_bapi-TYPE = 'E' OR
 it_return_bapi-TYPE = 'A'.
 MESSAGE it_return_bapi-message type 'I'.
 ENDIF.
 ENDLOOP.
2 . CRM_ORDER MAINTAIN used in another version of the program, return us the new position but unfortunately it create PRICE CONDITIONS INACTIVE, filled with 0.
So far we do not know why it create inactive conditions, especially the price one as, this condition is not statistical.
The code is the following:
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
 EXPORTING
 IT_BILLING = it_billing_maintain
 IT_SCHEDLIN_I = IT_SCHEDLIN_maintain
 IT_PRIDOC = IT_PRIDOC
 IT_TEXT = IT_TEXT
 IMPORTING
 ET_EXCEPTION = ET_EXCEPTION
 CHANGING
 CT_ORDERADM_H = CT_ORDERADM_H
 CT_ORDERADM_I = CT_ORDERADM_I
 CT_INPUT_FIELDS = CT_INPUT
 CT_DOC_FLOW = CT_DOC_FLOW
 EXCEPTIONS
 ERROR_OCCURRED = 1
 DOCUMENT_LOCKED = 2
 NO_CHANGE_ALLOWED = 3
 NO_AUTHORITY = 4
 OTHERS = 5.
Any suggestions are welcomed.
Many thanks in advance,
Andrea

Hi Amit,
basically we checked all input fields.
We noticed that input fields are set up exatly as you said as for
ORDERADM_H is A and for ORDERADM_I is B.
Unfortunately it still does not work. We think that input fields may be wrong.
Attached you find the code use for this BAPI.
In any case many thanks for your answer.
Andrea.
FORM rellenar_input_fields .
inicio modificacion jgarciar 11122006 ********************
rellenar tabla input_fields con datos de header
loop at it_header.
 it_inputfields-REF_GUID = it_header-GUID.
 it_inputfields-REF_KIND = 'A'.
 it_inputfields-OBJECTNAME = 'ORDERADM_H'.
 append it_inputfields.
 ct_input-REF_GUID = it_header-GUID.
 ct_input-REF_KIND = 'A'.
 ct_input-OBJECTNAME = 'ORDERADM_H'.
 ct_input-fieldname = 'GUID'.
 append ct_input.
endloop.
loop at it_header.
 CT_INPUT-REF_GUID = it_header-GUID.
 CT_INPUT-REF_KIND = 'A'.
 CT_INPUT-FIELDNAME = 'OBJECT_ID'.
 CT_INPUT-OBJECTNAME = 'ORDERADM_H'.
 ct_input-changeable = 'A'.
 append CT_INPUT.
endloop.
Fin modificacion jgarciar 11122006 ********************
Rellenar tbla input_fields de billing
LOOP AT it_billing_maintain INTO wa_billing_maintain.
Inicio modificacion jgarciar 11122006 ***************
 REFRESH WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 ***************
 CLEAR: WA_INPUT, WA_NOMBRES.
Datos de facturacion
 WA_INPUT-REF_GUID = wa_billing_maintain-ref_guid.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'BILLING'.
 WA_input-FIELDNAME = 'BILLING_BLOCK'.
 WA_NOMBRES-FIELDNAME = 'BILLING_BLOCK'.
 WA_NOMBRES-changeable = ''.
Inicio modificacion jgarciar 11122006 ************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 ************
Inicio modificacion jgarciar 11122006 ************
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 append WA_INPUT TO CT_INPUT.
Fin modificacion jgarciar 11122006 ************
ENDLOOP.
rellenar tabla input_fields con datos de item
loop at CT_ORDERADM_I INTO WA_CT_ORDERADM_I.
Inicio modificacion jgarciar 11122006 ******************
 SELECT SINGLE * FROM CRMD_ORDERADM_I
 WHERE GUID = WA_CT_ORDERADM_I-GUID.
Si existe, solo se modifica la descripcion
 IF sy-subrc = 0.
Fin modificacion jgarciar 11122006 ********************
MMG - Description
 CLEAR WA_INPUT.
Inicio modificacion jgarciar 11122006 **************
 REFRESH WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 **************
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_input-FIELDNAME = 'DESCRIPTION'.
 WA_input-CHANGEABLE = ''.
 WA_NOMBRES-FIELDNAME = 'DESCRIPTION'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 **************
 WA_NOMBRES-FIELDNAME = 'MODE'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 append wa_input to ct_input.
 CLEAR WA_INPUT.
 CLEAR WA_INPUT.
Inicio modificacion jgarciar 11122006 **************
 REFRESH WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 **************
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_input-FIELDNAME = 'MODE'.
 WA_input-CHANGEABLE = ''.
 WA_NOMBRES-FIELDNAME = 'DESCRIPTION'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 **************
 WA_NOMBRES-FIELDNAME = 'MODE'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 append wa_input to ct_input.
 CLEAR WA_INPUT.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
Fin modificacion jgarciar 11122006 **************
Inicio modificacion jgarciar 11122006 ***************
 endif.
 SELECT SINGLE * FROM CRMD_ORDERADM_I
 WHERE GUID = WA_CT_ORDERADM_I-GUID.
Si existe, solo se modifica la descripcion
 IF sy-subrc <> 0.
 clear wa_input.
MMG - GUID
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
Inicio modificacion jgarciar 11122006 **************
 REFRESH WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 **************
 WA_input-FIELDNAME = 'GUID'.
 WA_NOMBRES-FIELDNAME = 'GUID'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 append wa_input to ct_input.
 CLEAR WA_INPUT.
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
Inicio modificacion jgarciar 11122006 **************
 REFRESH WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 **************
 WA_input-FIELDNAME = 'DESCRIPTION'.
 WA_NOMBRES-FIELDNAME = 'GUID'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 append wa_input to ct_input.
 CLEAR WA_INPUT.
Fin modificacion jgarciar 11122006 **************
MMG -HEADER
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_input-FIELDNAME = 'HEADER'.
 WA_NOMBRES-FIELDNAME = 'HEADER'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 **************
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_input-FIELDNAME = 'PRODUCT'.
 WA_NOMBRES-FIELDNAME = 'PRODUCT'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 append WA_INPUT TO CT_INPUT.
 CLEAR WA_INPUT.
Fin modificacion jgarciar 11122006 **************
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 WA_input-FIELDNAME = 'ORDERED_PROD'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'ORDERED_PROD'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 append WA_INPUT TO CT_INPUT.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 CLEAR WA_INPUT.
Fin modificacion jgarciar 11122006 **************
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_input-FIELDNAME = 'ITM_TYPE'.
 WA_NOMBRES-FIELDNAME = 'ITM_TYPE'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 append WA_INPUT TO CT_INPUT.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 CLEAR WA_INPUT.
Fin modificacion jgarciar 11122006 **************
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_input-FIELDNAME = 'PARTNER_PROD'.
 WA_NOMBRES-FIELDNAME = 'PARTNER_PROD'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 ***************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 ***************
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_input-FIELDNAME = 'NUMBER_INT'.
 WA_NOMBRES-FIELDNAME = 'NUMBER_INT'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 append WA_INPUT TO CT_INPUT.
 CLEAR WA_INPUT.
Fin modificacion jgarciar 11122006 **************
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
MMG - 18-11-04
 WA_NOMBRES-FIELDNAME = 'NUMBER_EXT'.
 WA_NOMBRES-CHANGEABLE = ''.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 IF WA_CT_ORDERADM_I-ITM_TYPE <> 'ZTAD'.
 IF WA_CT_ORDERADM_I-NUMBER_PARENT <> ''.
MMG - PARENT
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_input-FIELDNAME = 'PARENT'.
 WA_NOMBRES-FIELDNAME = 'PARENT'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 append WA_INPUT TO CT_INPUT.
 CLEAR WA_INPUT.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
Fin modificacion jgarciar 11122006 **************
MMG - NUMBER_PARENT
 WA_INPUT-REF_GUID = WA_CT_ORDERADM_I-GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'ORDERADM_I'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_input-FIELDNAME = 'NUMBER_PARENT'.
 WA_NOMBRES-FIELDNAME = 'NUMBER_PARENT'.
 WA_NOMBRES-CHANGEABLE = ''.
Inicio modificacion jgarciar 11122006 **************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 append wa_input to ct_input.
 CLEAR WA_INPUT.
Fin modificacion jgarciar 11122006 **************
 ENDIF. "<> ZTAD
 ENDIF.
Inicio modificacion jgarciar 11122006 ***************
Fin modificacion jgarciar 11122006 ***************
endloop.
rellenar tabla input_fields con datos de item
loop at ct_orderadm_i.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'GUID'.
 append ct_input.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'HEADER'.
 append ct_input.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'PRODUCT'.
 append ct_input.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'ORDERED_PROD'.
 append ct_input.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'ITM_TYPE'.
 append ct_input.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'PARTNER_PROD'.
 append ct_input.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'NUMBER_INT'.
 append ct_input.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'NUMBER_EXT'.
 append ct_input.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'PARENT'.
 append ct_input.
 ct_input-REF_GUID = ct_orderadm_i-GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'ORDERADM_I'.
 ct_input-FIELDNAME = 'NUMBER_PARENT'.
 append ct_input.
endloop.
rellenar tabla input_fields con datos de item
Rellenar input fields con campos de doc_flow
Loop At ct_doc_flow Into wa_ct_doc_flow.
 REFRESH WA_INPUT-FIELD_NAMES.
 wa_input-REF_GUID = wa_ct_doc_flow-REF_GUID.
 wa_input-REF_KIND = wa_ct_doc_flow-REF_KIND.
 wa_input-OBJECTNAME = 'DOC_FLOW'.
 wa_nombres-fieldname = 'REF_GUID'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 wa_nombres-fieldname = 'REF_KIND'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 wa_nombres-fieldname = 'OBJTYPE_A'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 wa_nombres-fieldname = 'OBJTYPE_B'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 wa_nombres-fieldname = 'OBJKEY_A'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 wa_nombres-fieldname = 'OBJKEY_B'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 wa_nombres-fieldname = 'VONA_KIND'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 wa_nombres-fieldname = 'RELTYPE'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 wa_nombres-fieldname = 'BREL_KIND'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
EndLoop.
rellenar tabla input_fields con datos de sales
loop at it_sales.
 WA_INPUT-REF_GUID = it_sales-REF_GUID.
 WA_INPUT-REF_KIND = it_sales-REF_KIND.
 WA_INPUT-OBJECTNAME = 'SALES'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'PO_NUMBER_SOLD'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
endloop.
rellenar tabla input_fields con datos de organización
loop at it_organiz.
 WA_INPUT-REF_GUID = it_organiz-REF_GUID.
 WA_INPUT-REF_KIND = 'A'.
 WA_INPUT-OBJECTNAME = 'ORGMAN'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'SALES_ORG_RESP'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
endloop.
rellenar tabla input_fields con datos de SCHEDULELINE
loop at it_repartos.
 WA_INPUT-REF_GUID = it_repartos-ITEM_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'SCHEDLIN'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'QUANTITY'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
endloop.
Inicio modificacion jgarciar 11122006 ********************
Datos de schedulin - Cantidades
loop at IT_SCHEDLIN_MAINTAIN INTO WA_IT_SCHEDLIN_MAINTAIN.
 WA_INPUT-REF_GUID = WA_IT_SCHEDLIN_MAINTAIN-REF_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'SCHEDLIN'.
Inicio modificacion jgarciar 11122006 *****************
 REFRESH WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 *****************
 WA_NOMBRES-FIELDNAME = 'QUANTITY'.
Inicio modificacion jgarciar 11122006 *****************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 *****************
 INSERT WA_INPUT INTO TABLE CT_INPUT.
endloop.
Fin modificacion jgarciar 11122006 ********************
rellenar tabla input_fields con datos de CONDITION_COM
loop at it_pridoc into wa_pridoc.
 WA_INPUT-REF_GUID = wa_pridoc-REF_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'PRIDOC'.
Inicio modificacion jgarciar 11122006 *****************
 REFRESH WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 *****************
 WA_NOMBRES-FIELDNAME = 'CURRENCY'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'COND_TYPE'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'COND_RATE'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'COND_P_UNT'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
Mod. 04.12.2006 ASA INICIO.
 WA_NOMBRES-FIELDNAME = 'KSCHL'.
Inicio modificacion jgarciar 11122006 *****************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-field_names.
Fin modificacion jgarciar 11122006 *****************
 WA_NOMBRES-FIELDNAME = 'WAERS'.
Inicio modificacion jgarciar 11122006 *****************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-field_names.
Fin modificacion jgarciar 11122006 *****************
 WA_NOMBRES-FIELDNAME = 'KBETR'.
Inicio modificacion jgarciar 11122006 *****************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-field_names.
 WA_NOMBRES-FIELDNAME = 'KPEIN'.
Inicio modificacion jgarciar 11122006 *****************
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-field_names.
Fin modificacion jgarciar 11122006 *****************
 INSERT WA_INPUT INTO TABLE CT_INPUT.
Mod. 04.12.2006 ASA FINAL.
endloop.
MMG - Input fields para los textos
Inicio modificacion jgarciar 11122006 ********************
loop at it_text into wa_it_text.
 clear wa_input.
 WA_INPUT-REF_GUID = wa_it_text-REF_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'TEXTS'.
 wa_input-fieldname = 'TDID'.
 APPEND WA_INPUT TO CT_INPUT.
 clear wa_input.
 WA_INPUT-REF_GUID = wa_it_text-REF_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'TEXTS'.
 wa_input-fieldname = 'TDSPRAS'.
 APPEND WA_INPUT TO CT_INPUT.
 clear wa_input.
 WA_INPUT-REF_GUID = wa_it_text-REF_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'TEXTS'.
 wa_input-fieldname = 'TDSTYLE'.
 APPEND WA_INPUT TO CT_INPUT.
 clear wa_input.
 WA_INPUT-REF_GUID = wa_it_text-REF_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'TEXTS'.
 wa_input-fieldname = 'MODE'.
 APPEND WA_INPUT TO CT_INPUT.
 clear wa_input.
 WA_INPUT-REF_GUID = wa_it_text-REF_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'TEXTS'.
 wa_input-fieldname = 'LINES'.
 APPEND WA_INPUT TO CT_INPUT.
 clear wa_input.
 WA_INPUT-REF_GUID = wa_it_text-REF_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'TEXTS'.
 wa_input-fieldname = 'TDFORMAT'.
 APPEND WA_INPUT TO CT_INPUT.
 clear wa_input.
 WA_INPUT-REF_GUID = wa_it_text-REF_GUID.
 WA_INPUT-REF_KIND = 'B'.
 WA_INPUT-OBJECTNAME = 'TEXTS'.
 wa_input-fieldname = 'TDLINE'.
 APPEND WA_INPUT TO CT_INPUT.
Inicio modificacion jgarciar 11122006 *****************
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'TDID'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'TDSPRAS'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'TDSTYLE'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'MODE'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'LINES'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'TDFORMAT'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 WA_NOMBRES-FIELDNAME = 'TDLINE'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
Fin modificacion jgarciar 11122006 *****************
 INSERT WA_INPUT INTO TABLE CT_INPUT.
endloop.
Fin modificacion jgarciar 11122006 ********************
rellenar tabla input_fields con datos de PARTNER
loop at it_partner.
 WA_INPUT-REF_GUID = it_partner-REF_GUID.
 WA_INPUT-REF_KIND = it_partner-REF_KIND.
 WA_INPUT-OBJECTNAME = 'PARTNER'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_INPUT-LOGICAL_KEY = it_partner-REF_PARTNER_HANDLE.
 WA_NOMBRES-FIELDNAME = 'PARTNER_FCT'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 WA_INPUT-REF_GUID = it_partner-REF_GUID.
 WA_INPUT-REF_KIND = it_partner-REF_KIND.
 WA_INPUT-OBJECTNAME = 'PARTNER'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_INPUT-LOGICAL_KEY = it_partner-REF_PARTNER_HANDLE.
 WA_NOMBRES-FIELDNAME = 'PARTNER_NO'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 WA_INPUT-REF_GUID = it_partner-REF_GUID.
 WA_INPUT-REF_KIND = it_partner-REF_KIND.
 WA_INPUT-OBJECTNAME = 'PARTNER'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_INPUT-LOGICAL_KEY = it_partner-REF_PARTNER_HANDLE.
 WA_NOMBRES-FIELDNAME = 'NO_TYPE'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 WA_INPUT-REF_GUID = it_partner-REF_GUID.
 WA_INPUT-REF_KIND = it_partner-REF_KIND.
 WA_INPUT-OBJECTNAME = 'PARTNER'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_INPUT-LOGICAL_KEY = it_partner-REF_PARTNER_HANDLE.
 WA_NOMBRES-FIELDNAME = 'DISPLAY_TYPE'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 WA_INPUT-REF_GUID = it_partner-REF_GUID.
 WA_INPUT-REF_KIND = it_partner-REF_KIND.
 WA_INPUT-OBJECTNAME = 'PARTNER'.
 REFRESH WA_INPUT-FIELD_NAMES.
 WA_INPUT-LOGICAL_KEY = it_partner-REF_PARTNER_HANDLE.
 WA_NOMBRES-FIELDNAME = 'KIND_OF_ENTRY'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
endloop.
JCF 19/12/2003 Incorporar funcionalidad fechas de ZSUBIROFERTA
Rellenar input_fields con datos de appointment
LOOP AT it_appointment.
 WA_INPUT-REF_GUID = it_appointment-ref_guid.
 WA_INPUT-REF_KIND = 'A'.
 WA_INPUT-OBJECTNAME = 'APPOINTMENT'.
 REFRESH WA_INPUT-FIELD_NAMES.
 if it_appointment-APPT_TYPE = 'ZLIQUIDACION'.
 WA_INPUT-LOGICAL_KEY = 'ZLIQUIDACIONX'.
 ELSE.
 WA_INPUT-LOGICAL_KEY = it_appointment-APPT_TYPE.
 ENDIF.
 WA_NOMBRES-FIELDNAME = 'APPT_TYPE'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 wa_input-fieldname = 'APPT_TYPE'.
 append wa_input to ct_input.
 WA_INPUT-REF_GUID = it_appointment-ref_guid.
 WA_INPUT-REF_KIND = 'A'.
 WA_INPUT-OBJECTNAME = 'APPOINTMENT'.
 REFRESH WA_INPUT-FIELD_NAMES.
 if it_appointment-APPT_TYPE = 'ZLIQUIDACION'.
 WA_INPUT-LOGICAL_KEY = 'ZLIQUIDACIONX'.
 ELSE.
 WA_INPUT-LOGICAL_KEY = it_appointment-APPT_TYPE.
 ENDIF.
 WA_NOMBRES-FIELDNAME = 'TIMESTAMP_FROM'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 wa_input-fieldname = 'APPT_TYPE'.
 append wa_input to ct_input.
 WA_INPUT-REF_GUID = it_appointment-ref_guid.
 WA_INPUT-REF_KIND = 'A'.
 WA_INPUT-OBJECTNAME = 'TIMESTAMP_FROM'.
 REFRESH WA_INPUT-FIELD_NAMES.
 if it_appointment-APPT_TYPE = 'ZLIQUIDACION'.
 WA_INPUT-LOGICAL_KEY = 'ZLIQUIDACIONX'.
 ELSE.
 WA_INPUT-LOGICAL_KEY = it_appointment-APPT_TYPE.
 ENDIF.
 WA_NOMBRES-FIELDNAME = 'TIMEZONE_FROM'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 wa_input-fieldname = 'TIMEZONE_FROM'.
 append wa_input to ct_input.
 WA_INPUT-REF_GUID = it_appointment-ref_guid.
 WA_INPUT-REF_KIND = 'A'.
 WA_INPUT-OBJECTNAME = 'APPOINTMENT'.
 REFRESH WA_INPUT-FIELD_NAMES.
 if it_appointment-APPT_TYPE = 'ZLIQUIDACION'.
 WA_INPUT-LOGICAL_KEY = 'ZLIQUIDACIONX'.
 ELSE.
 WA_INPUT-LOGICAL_KEY = it_appointment-APPT_TYPE.
 ENDIF.
 WA_NOMBRES-FIELDNAME = 'TIMESTAMP_TO'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 wa_input-fieldname = 'TIMESTAMP_TO'.
 append wa_input to ct_input.
 WA_INPUT-REF_GUID = it_appointment-ref_guid.
 WA_INPUT-REF_KIND = 'A'.
 WA_INPUT-OBJECTNAME = 'APPOINTMENT'.
 REFRESH WA_INPUT-FIELD_NAMES.
 if it_appointment-APPT_TYPE = 'ZLIQUIDACION'.
 WA_INPUT-LOGICAL_KEY = 'ZLIQUIDACIONX'.
 ELSE.
 WA_INPUT-LOGICAL_KEY = it_appointment-APPT_TYPE.
 ENDIF.
 WA_NOMBRES-FIELDNAME = 'TIMEZONE_TO'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 wa_input-fieldname = 'TIMEZONE_TO'.
 append wa_input to ct_input.
 WA_INPUT-REF_GUID = it_appointment-ref_guid.
 WA_INPUT-REF_KIND = 'A'.
 WA_INPUT-OBJECTNAME = 'APPOINTMENT'.
 REFRESH WA_INPUT-FIELD_NAMES.
 if it_appointment-APPT_TYPE = 'ZLIQUIDACION'.
 WA_INPUT-LOGICAL_KEY = 'ZLIQUIDACIONX'.
 ELSE.
 WA_INPUT-LOGICAL_KEY = it_appointment-APPT_TYPE.
 ENDIF.
 WA_NOMBRES-FIELDNAME = 'DURATION'.
 INSERT WA_NOMBRES INTO TABLE WA_INPUT-FIELD_NAMES.
 INSERT WA_INPUT INTO TABLE CT_INPUT.
 wa_input-fieldname = 'DURATION'.
 append wa_input to ct_input.
endloop.
Fin JCF 19/12/2003 Incorporar funcionalidad fechas de ZSUBIROFERTA
Inicio modificacion jgarciar 11122006 ********************
rellenar tabla input_fields con datos de CONDITION_COM
loop at it_preciopos.
 CT_INPUT-REF_GUID = it_preciopos-REF_GUID.
 CT_INPUT-REF_KIND = 'B'.
 CT_INPUT-OBJECTNAME = 'CONDITION_COM'.
 CT_INPUT-FIELDNAME = 'CURRENCY'.
 append CT_INPUT.
 CT_INPUT-REF_GUID = it_preciopos-REF_GUID.
 CT_INPUT-REF_KIND = 'B'.
 CT_INPUT-OBJECTNAME = 'CONDITION_COM'.
 CT_INPUT-FIELDNAME = 'COND_TYPE'.
 append CT_INPUT.
 CT_INPUT-REF_GUID = it_preciopos-REF_GUID.
 CT_INPUT-REF_KIND = 'B'.
 CT_INPUT-OBJECTNAME = 'CONDITION_COM'.
 CT_INPUT-FIELDNAME = 'COND_RATE'.
 append CT_INPUT.
 CT_INPUT-REF_GUID = it_preciopos-REF_GUID.
 CT_INPUT-REF_KIND = 'B'.
 CT_INPUT-OBJECTNAME = 'CONDITION_COM'.
 CT_INPUT-FIELDNAME = 'COND_P_UNT'.
 append CT_INPUT.
endloop.
rellenar tabla input_fields con datos de sales
loop at it_sales.
 CT_INPUT-REF_GUID = it_sales-REF_GUID.
 CT_INPUT-REF_KIND = it_sales-REF_KIND.
 CT_INPUT-OBJECTNAME = 'SALES'.
 CT_INPUT-FIELDNAME = 'PO_NUMBER_SOLD'.
 append CT_INPUT.
endloop.
rellenar tabla input_fields con datos de pricing
loop at IT_PRICING.
 CT_INPUT-REF_GUID = it_pricing-REF_GUID.
 CT_INPUT-REF_KIND = it_pricing-REF_KIND.
 CT_INPUT-OBJECTNAME = 'PRICING'.
 CT_INPUT-FIELDNAME = 'PRICE_DATE'.
 append CT_INPUT.
endloop.
rellenar tabla input_fields con datos de organización
loop at IT_ORGANIZ.
 CT_INPUT-REF_GUID = it_organiz-REF_GUID.
 CT_INPUT-REF_KIND = 'A'.
 CT_INPUT-OBJECTNAME = 'ORGMAN'.
 CT_INPUT-FIELDNAME = 'SALES_ORG_RESP'.
 append CT_INPUT.
endloop.
LLenar tabla scheduline.
loop at it_repartos.
 ct_input-REF_GUID = it_repartos-ITEM_GUID.
 ct_input-REF_KIND = 'B'.
 ct_input-OBJECTNAME = 'SCHEDLIN'.
 ct_input-FIELDNAME = 'QUANTITY'.
 append ct_input.
endloop.
Fin modificacion jgarciar 11122006 ********************
ENDFORM. " rellenar_input_fields

Help needed in finding duplicate entries in invoices

Hi,
let me explian u the senario.
when we enter the invoice no. in vf03 and select any item and click on pricing button.
there i find the Cnty fild having duplicate entries like xr1 2 times and xr2,xr3,xr4,xr5 and xr6 all 2 times
so i need to write a query to find out which of all the invoices have these types of duplicate entries.
regards,
maqsood

Hi!
CnTy is header line of condition type column.
There can be several reasons, why conditions types are twice in a document. E.g. conditions can be given on header and line level, so they are two times in a document.
These tax conditions are just line level. But please check, if they have different colors. I currently don't remember if only the blue or only the black lines (with or without highlight) are relevant for the document.
The inactive conditions are still shown, but not 'counted'. You can set conditions inactive by requirements, by formula, by exclusion groups... so there are many ways to set the system up.
Only if your total is wrong you have to do something (e.g. give users a training how to create a sales order / invoice).
Conditions for invoice can be found in KONV with KONV-KNUMV = VBRK-KNUMV.
Regards,
Christian

Condition value is Inactive in sales order

Hi Friends,
I am facing the following problem,
In the sales order, it is picking all condition records as per pricing procedure and calculates perfectly. But in the header net value field it is not updating. It is showing one condition record value only.
During analysis I found that the all records is inactive except which one is updating in the net value field and reason is "Y - Inactive because of Subsequent Price."
Please help me to solve this issue.
Thanks in Advance.
Dilip

Dear Dilip
For information, when you have a condition record showing as
inactive it is because you have a base price condition record
somewhere below your discounts.
Check your condition records below the discounts, are
there any of condition class 'B'? If yes, then that is why they are inactive.
thanks
G. Lakshmipathi

Pricing condition type is inactive in pricing procedure

hi,
We have two base price in our pricing procedure ,
fixed -pr00
and wight wise.-pr01
both have condition class-B
while doing VA01 conditon type is showing as inactive(-Y-inactive because of subsequent price.
Please need ur help

Thanks for your early reply,my client do not want to make the !st conditiontype (PR00) as discount and surcharge.
let me elabrate the pricing procedure more detail.. we have two pricing procedure for export sales.
1-export sales -zabexp
2-Deemed export sales-zadexp
pricing procedure -zabexp
condition type                                     from      to      manual       required
proo(base price)                                      -            -         -                   -
pr01 (base price weight wise )                -           -           -                   -
it is runing well in zabexp. but the same setting is not running in zadexp.
Need Help.

To make the Pricing Condition types inactive in Pricing Procedure

Hi Experts,
I am facing a senario where, in a sales order, pricing procedure, if one of the pricing condition type does not exist, then two other condition types (even though they are determined by condition records), should be either made inactive or should not appear in the pricing procedure.
Example: If I have 3 condition types in Pricing Proc say
YYY1, YYY2, YYY3, then the scenarios are
a. If one of the condition types YYY1 is not determined, then, YYY2 and YYY3 should not be either determined in the sales order or should be made inactive. This same logic applies to both YYY2 and YYY3.
b. If all three condition types are determined in Pricing Proc of the sales order, then, the price should be considered.
If it was just YYY1 then, I could have done it in VOFM by writing a routine and assigning it to YYY2 and YYY3 in pricing proc. However, the scenario is to check the other condition types as well and make YYY1 inactive if any of the other condition type does not exist. Both condition types are determined after YYY1 which is another difficulty.
I tried creating a dummy condition type and assigning it to Pricing Proc (at the end of Pricing Proc). For this dummy condition I put in a pricing requirement which checks for all three condition types and if one does not exist, then it make other conitions inactive.
However, this does not work in VA02 and VA03 as XKOMV is either not getting filled up or even if is getting filled, it is not having the condition type. It some times has condition records, and sometimes not... (not very sure why)
So, I was thinking of using user exit for the same. However, I was unable to find a suitable user exit for the same where KONV table can be read or XKOMV can be filled.
Can you please suggest if any user exit can be used for this or if we can implement it in a different way?
Regards,
Mukund S

Hi,
I think you can use condition exclusion functionality to select best pricing condition from a set of conditions in pricing. You can compare conditions in many ways.
I believe you can plot a solution with little research. The below link is for your reference.
[http://help.sap.com/saphelp_40b/helpdata/fr/93/743483546011d1a7020000e829fd11/content.htm]

Sales Order Pricing - Condition Type:PR00 inactive

Hi
In Sales Order Item level pricing, condition type PR00 become inactive. It shows reason : Inactive via formulae of incorrect.
Sales Order is partially delivered & billed. For remaining deliveries, system not allowing for billing, showing sales order is incomplete.
Condition Type PR00 maintained manually. Order quantity changed several times.
Please guide me on this.
Regards
Uma

Dear Umasankar
Check in VK12 for the material whether the From To Date is maintained for current period.
Also go to V/08 and check your pricing procedure whether any invalid account key is defined.
Thanks
G. Lakshmipathi

Condition type inactive

hi all,
why condition type is inactive in sales order item level.
when i save invoice it shows error in pricing.
pls let me know.
Regards
Rams

You can get a better idea by going to the sales order at the item level in the condition tab, highlight your condition type and click on Analysis. It will give you an idea why it is inactive.
If it is a price condition type then there must another price condition type below so it is overwriting the first condition type.
Regards
AK

SD planned revenues from inactive price condition

Hello,
please assist.
Revenue elements from the SD pricing procedure (coditions) that are not statistical are updated as planned revenue on the sales order item (within table COSP with the business transaction SDOR).
The relevant revenue accounts are determined within the revenue account determination.
Is the revenue account determination processed also for SD conditions, which are inactive (KOMV-KINAK)?
We have got an issue, that also some conditions, which are inactive because of subsequent price (KOMV-KINAK=Y) are updated into the COSP-SDOR as planned revenue. Therefore the position has more planned revenue within the result analysis and as we use the revenue based result analysis method, it influences the WIP calculation.
Thanks in advance
P

Issue solved.
The reason was the SAP Note 1062462.
This note is used to extract also inactive conditions into BW. Unfortunatelly, due to this modification, the inactive conditions are not deleted from xmckomv, which is used also for updating the planned revenues (and other SIS statistics, which are based on the conditions), so they were added to the planned revenues.
We have to deimplement the note.

Condition Inactive

Similar Messages

Maybe you are looking for