Additional Branch Condition Type in but not documented in HTMLDB UG v1.6

I would like to understand this condition type for Branch processing:
When Process in Comma Delimited List of Process IDs Has Run
How are Process IDs known? Could an example using this condition be provided?
Thanks,
Kelly

Kelly - This is a condition type available everywhere, not just for branches. However, it has never been implemented. It is an error that we make it available in these LOVs.
Scott

Similar Messages

Additional VAT condition type is not flowing to PO

Dear All,
            An additional tax of 1 % is levied in State of gujurat and for this we can take the credit . It behaves exactly like VAT like it calculates its value as 1% of base amount and excise duty levied on it . But this condition is not available in standard TAXINN procedure . So we created a new procedure copying from TAXINN .We created a condition type copying from standard condition type JVRD that is for VAT on which we take credit .Then we assign this condition type to tax procedure immediately below condition type JVRD and it should calculate the value in the same way as that of VAT .Then we assigned this procedure to India , assigned all the condition types in CIN config and maintained default condition types for this procedure copying from TAXINN .
            But while we are creating a PO after that ,this additional tax condition type is not flowing in it .
Can anybody let me know where is the missing link in this customisation .
Regards
Abhijit Das

Hi AP ,
         The condition type is Valid from : Todays Date and valid to 31.12.9999 . Is there any problem with this ?
Abhijit

Purchase order one particular condition type vale should not inventorised

Dear All,
I have a scenario in the purchase order particular one condition type value should not get inventorised that should goes to a seperate account. it should not added with material cost
i have created a seperate condition type ZZ01
with condition class : A - Discount or surcharge
calcualtion type : A - Percentage
and i have attached this condition type to pricing procedure in accurals i have maintained a seperate posting transaction.
the amount is getting posted against the accural transaction event key.
but its getting inventorised with material cost it should not get inventorised..
what is the procedure...
Regards
Anand.
Edited by: Anandhakumar Palanisamy on Mar 24, 2010 1:17 PM

Hi..
I have maintained for this condition type Accurals in M/06
and i have maintained the Statistical tick mark in pricing procedure..
but its getting inventorised...
it should not inventorised...
any other solution...
Regards
P.Anandhakumar

Condition type freight is not getting displayed in print preview

Hi,
I created PO, and while seeing its print preview:
Condition type freight is not getting displayed.
Where i missed?
Uts

hi,
Inddition to M/08...(As given above)...
Also do check the smart form or SAP script...used for the output...check it with the ABAPer...whether the field is liable for o/p or not??
Smart form is attached at message type of message determination..
Regards
Priyanka.P

Condition type in contract not reflecting on to the PO release

Hi All,
I have a contract wherein i have two condition types which are set i.e. PB00 and ZM07. Now i've made some changes and removed ZM07 and instead put ZM05.
This new condition type (ZM05) is not reflecting on to the PO already released or on to the new line items that are being added to the already existing PO's. Kindly let me know what/where to change to effect ZM05 on the line items of release orders.

Hi,
One thing you could try is the Update button on the item Conditions detail tab. Run the selection for B Carry out new pricing
C Copy manual pricing elements and redetermine the others
"B" is pretty good for adding in new condition types that are added after the PO has been created.
Regards.

Running KE27. Getting an error " Condition type XX12 is not active"

Hi There -
When running KE27 getting an error Copa Validation: Condition Type XX12 is not active.
Appreciate your time.
Thanks
Sri

Hi Sri,
is this a standard erromessage? Which code (ex: XY123)?
br, Guido

Condition type in PO not posting to desired transaction key.

Dear experts,
I was wondering whether someone could help me with the following:
I have defined a condition type for which specific additive costs for a purchased finished good should be added. The material is valued at standard price with the specifics that prior to the price calculation via transaction CK74N, additive costs are calculate and then added when executing CK11N that is composed of the price of the purchased finished good and the additive costs. We have created a condition type to break down the additive costs in the one hand and the material cost on the other. We want to have these costs to be posted against a specific cost account. We have created a transaction (via OBYC) for that and added it to the calculation schema. However, when posting the Goods Receipt, the additive costs (difference between the standard price and material price in the PO) are not posted to the desired transaction/GL account but to the price difference account (transaction PRD).
Could anyone please provide me with the customizing steps I should follow to succeed in the flow we want to implement? Can this desired outcome be done via standard or should any User Exit or programming be done to get the expected results?
Thanks in advance and regards,
David.

hi
Standard SAP Post the difference only with PRD account.

Condition type in PO not posting to desired transaction

Dear experts,
I was wondering whether someone could help me with the following:
I have defined a condition type for which specific additive costs for a purchased finished good should be added. The material is valued at standard price with the specifics that prior to the price calculation via transaction CK74N, additive costs are calculate and then added when executing CK11N that is composed of the price of the purchased finished good and the additive costs.
Next, we have created a condition type to break down the additive costs in the one hand and the material cost on the other. We want to have these costs to be posted against a specific cost account. We have created a transaction (via OBYC) for that and added it to the calculation schema. However, when posting the Goods Receipt, the additive costs (difference between the standard price and material price in the PO) are not posted to the desired transaction/GL account but to the price difference account (transaction PRD).
Could anyone please provide me with the customizing steps I should follow to succeed in the flow we want to implement?
Thanks in advance for your kind support.
Eric

Hi again,
Do you know what steps we should take in order to modify the standard functionality to have the part of the standard cost asigned to the condition type post to its transaction and not to the standard PRD transaction?
Thanks and Regards,
Eric

Additional Pricing Condition Type Determination in Returns Oder

Hi Guys
I am working on Returns Sales Process, but I have stuck in pricing?
The thing is I have to determine the additional condition type based on transaction type .i.e. returns order when I create the returns order with ref. to sales order the pricing condition types which is present in the sales order has been copied but the additional condition type is not determined automatically?
I have created the 2 pricing procedure one of sales order and other for returns order.
Can anybody help me out?
Thanks advance

Hi,
All you have done is right. just assign the other pricing proceduere which you created for the document re.
To the combination of sales orgdistribution chaneldivision + cpp( in customer master)+ dpp( for the document re )
So now when you create with the re doument you will automatically get that pricing procedure.
hope this solves.
regrds\
preetham

Condition record exist but not set in SO

Hi SDN Team,
I have a problem. Where in the sales order for the Discount condition type condition record where already exist in diffferent validity period.
EG
ZAJ1 discount condition type - with the same key combination with different valididity period
EG:
ZAJ1 - 27.01.2009 to 15.02.2009
ZAJ1 - 16-02-2009 to 15-03-2009
The reason is not set for the ZAJ1 condition in the Sales Order is due to the sales order was created before the pricing condition record validity datet. Sales order where created on 11.02.2009. But the condition record where valid from 16.02.2009 that is the reason the condition record was not set in the sales order.
Based on this explanation user agreed and the call was closed.
I have also explained Where ZAJ1 has condition record. but which is not set in the document. if pricing was carried out again it will set the condition for the item.
But now again the call was reopened stating that -
At the time of creating the sales order the ZAJ1Condition record exist in the period 27-01-2009 to 15-02-2009. now the primary rebate should be used by the system. Unfortunately it did not.
Based on the reopend call - i have further investigated the issue but i could not find the root cause.
Based on this when i checked the previous order where the ZAJ1 condition was well picked up with the validity period 27-01-2009 to 15-02-2009, what might be the reason the condition type was not picked up in the sales order?
Can you please let me know with your expertise in solving this issue.
Regards,
J

1)Requirement is set with 2 (itme with pricing). and calculation type is assigned with own calculation type.
2) In the pricing analysis - it shows as per below
This message tells you that the condition record exists, but has not been set in the document. If pricing was carried out again for the document item, then the condition would be set.
There are different reasons for this:
The condition was deleted manually in the item condition screen.
The condition record was created later. Please note that order processing and pricing have buffer mechanisms. This means that a newly added condition record might only be found after order processing has been left completely and then started again.
If the condition type is used for subsequent settlement (rebate), there may be subsequent updating of business volume (the agreement is is created retrospectively). The document conditions do not contain the condition record, as the condition record was not created when pricing was carried out. Updating of business volume is carried out using special functions for subsequent settlement.
When an item was added, the condition record was accessed with key fields other than change time. This could lead to different results in the requirements check at the time of adding and the change time. This can occur when modifications are made.
In billing (or when copying orders): Certain condition types were not determined in the source document (this is usually controlled by the pricing requirements). When creating the document, the document flow (TVCPF,TVCPA) is processed using a pricing type that does not redetermine these condition types, although they are supposed to be called via the requirements.
Thanks,
J

Condition type VPRS is not available in ke24

Dear Experts,
My clients wants to analyze cogs in transaction code ke24. I can see a overview of stratification costs, however the cogs value is not available. I made the assignment between condition type(VPRS) and value field in KE4I. but it didn't work. May you help me??
Thanks
Marcel

HI Marcel,
Please check KE4W if the value field is reset here. Also please check note 20254 which explains which value should be transfered to CO-PA from SD.
Regards.
Abhisek

Message output condition typ for PO not getting defaulted during PO create

Hi,
I have created a ZNEU output type for purchase order print out for ZNB purchase document type by copying the stndard NEU output type ,
I have mainatined the condition record in NACE for ZNEU out put type against the Purchase docuemnt type ZNB, but when i create a PO and save i am not getting the ZNEU message output type as default in PO,
Kindy provide your valuable input.
My requirement is to default z output type in PO

Hi
SPRO-MM-Purchasing-messages-ouput control-message type-define message type for PO-Fine tuned control PO
Here you can define which message type needs to be defaulted
Regards
Sandeep

Condition type EDI1 is not populating in XKOMV for BOM Header Item

Hi All,
We have assgined EDI1 and EDI2 condition types in pricing procedure, and creating orderd through Idoc, and checking for customer expected price.
EDI1 and EDI2 are correctly populating for standard items, but NOT for BOM header item.
I checked in XKOMV and observed that EDI1 is not coming for BOM header item.
Please advise what to do.
Regards

Hi,
In case your pricing procedure is similar to standard SAP then probably you use calculation routine 8 for EDI1 and EDI2.
8 is represented by routine FV64A008. Inside this routine there is the following check:
check: komp-prsfd = 'X'.
Verify if your BOM header item category has switched on Pricing indicator (TVAP-PRSFD). If you have blank value there then this is the reason why EDI1 / EDI2 condition don't receive value in your case.
Best regards
Witek Prawecki

Additional RFQ Condition Types

Dear All ,
         I am trying to create a RFQ .The condition types I can find init to maintain are
P000 : Gross Price
R000 : Discount On gross
R001 : Discount Of quantity
R002 : Absolute Discount
R003 : Discount % on net
           But my client requires more condition types like Packing & Forwarding ,Excise , CESS , VAT /CST , FREIGHT .
           I want to know how I will enter these condition types in RFQ . How RFQ is having this procedure ? This is not picked from vendor schema group .

Hi,
You will get this condition types while entring the Quotation in ME47 transaction based on the vendor.
Regards,
Bharat.

Addition of Condition type in XKOMV programmatically - Sales Order creation

Hi,
I need to add a condition type ( a record with whole data like Amount etc,.) in XKOMV programmatically during a Sales order creation, so that the new condition type gets automatically saved along with other data in VA01. Please suggest the better way of doing this - through Userexits or Form routines.
Thanks in Advance,
Sirisha.
Edited by: hema Namuduri on Oct 20, 2011 5:12 PM
Edited by: hema Namuduri on Oct 20, 2011 5:13 PM

Hi E_Hinojosa / madhurao123,
I added the below code in FORM userexit_xkomv_bewerten_end ( of Include: RV61AFZB ) which will get triggered in 'Pricing' Function Module.
      FORM USEREXIT_XKOMV_BEWERTEN_END                              *
FORM userexit_xkomv_bewerten_end.
DATA: l_amt1 TYPE vbak-netwr,
            v_waerk TYPE waerk.
l_amt1 = '56000'.    " Let's say..
          READ TABLE xkomv WITH KEY kschl = 'ZF02 '.
          IF sy-subrc <> 0.
              xkomv-stunr = '012 '.
              xkomv-kschl = 'ZF02 '.
              xkomv-krech = 'B    '.
              xkomv-kwert = l_amt1.
              xkomv-kbetr = l_amt1.
              xkomv-ksteu = 'C'.
Select single waerk into v_waerk from vbak where vbeln = komp-vgbel.
              IF v_waerk <> space.
                xkomv-waers = v_waerk.
              ENDIF.
              xkomv-zaehk = 99.
              CLEAR: xkomv-kntyp,
                     xkomv-kstat,
                     xkomv-kolnr,
                     xkomv-knumh,
                     xkomv-kopos,
                     xkomv-kinak.
              xkomv-kherk = 'C'.
              xkomv-kvsl1 = 'ERL '.
              xkomv-drukz = 'X'.
              xkomv-kaend_loe = 'X'.
              xkomv-updkz = 'I'.
              APPEND xkomv. CLEAR xkomv.
              DELETE xkomv WHERE kschl = 'ZH00 ' OR kschl = 'ZF00 '.
              komp-netwr = l_amt1.
            ENDIF.
ENDFORM.                    "USEREXIT_XKOMV_BEWERTEN_END
Above is the main logic I am using, apart from other Export, Import statements etc,.The above code is getting triggered during every screen transition.
It is automatically adding condition type 'ZF02' with all values during the creation of sales orders for some contracts, but not for other contracts. I am trying to trace what is the difference in both scenarios.
Please suggest.
Regards,
Sirisha N.

Additional Branch Condition Type in but not documented in HTMLDB UG v1.6

Similar Messages

Maybe you are looking for