system is not fetching condition record maintained for region level

[former_member1269750]

Hi

I did some rearrangemt of tables under access sequence on quality server.

system is fetching data frm c.records with older arrangment of tables on production server. I want to test with newer sequence on quality. How can it be possibile?

checked released status of tables .Green.ok

Regards,

Sachin

[former_member1269750 · Accepted solution]

This message was moderated.

[former_member1269750 · Accepted solution]

Plz find c.table image as below.

pLZ WRITE if any correction to fetch that c.record frm system

[Former Member · Accepted solution]

This message was moderated.

[Former Member · Accepted solution]

Hi sachin,

               If the region to be picked up is the region of the customer then the field for region of the customer is REGIO not J_1AREGIO. Please create the table with the 2nd region from field catelog where the field name should be REGIO, as you have created with J_1AREGIO.

Thanks & Regards

      Imran

[former_member1269750]

i want to fetch data from c.table as below :

Sales org./Distr. Chl/Division/Region/Material 

System is showing as ' access not made (intialized field) ' when doing Analysis pricing.

pls write solution

[Shiva_Ram]

Try below;

Go to t.code V/07 ,click on utilities button on the top. Then in the next screen enter the access sequence that you have newly created and execute. Then test by creating new documents.

Regards,

[sourabh_jain66]

Hi Sachin,

Are you trying to change an old order or creating new order, probably creation of new order will solve the issue, if not then check in document if region is being fatched in document.

Also check in access sequence for processing status, is that is there or not.

Rgds

Sourabh

[former_member1269750]

Hi shivram

tested as per told u.still not fetching record. processing status is active.

Need alternate soln

sachin

[former_member1269750]

Hi sourabh

checked all. made new order.c.record

still not fetching c.record.

Need alternate soln

Sachin

[sourabh_jain66]

Hi Sachin,

What does long text for pricing analysis in order says in this case.

Also try to create a new access sequence with same accesses and check if that solves your issue.

Rgds

Sourabh

[Former Member]

Hi,

it may happen you have assigned nay routine in pricing procedure for that cond type . which may not match the requirement . so that it delete the cond record.

If yes check with the ABAP'er for details about the requirement .

Regards

Pitabash

[former_member1269750]

Hi Pitabash

where is routine no in c.type ? not able to find it

i and ABAPer searched for VOFM.I need to find routine no assigned to c,type. where it is ?

Sachin Karale

[sourabh_jain66]

You can find the routine in your pricing procedure against condition type, check if anything assigned thre.

Rgds

Sourabh

[former_member1269750]

i think no routine is assigned

Reqt : 0

Calc Type : 0

mentioned in pricing procedure against c.type.

sachin

[former_member1269750]

PLZ find image

[Former Member]

HI,

According to your screen shot it shows that it is a Discount condition . So you need to check below things.

Is you condition type calculated on (%) Percentage basis. if yes check is there any  price for condition type ZPWT, because you have mention from TO as 475 . so It ll calculate on that cond type only.

Check the Analysis for that condition type and access sequence and access. what it shows. It may fail due to previous active  access. . So check details in Analysis.

Regards

Pitabash

[former_member1269750]

[former_member1269750]

as shown in the image, if i maintain and test price wrt diiferent c.tables created under c.type ZPTR.After price analysis in the order, system is taking price from every c.record except from region wise. i dont think there is problem with % basis calculation or any previous active c.type. Reason has be different one. sachin

[od_manikandan]

Hai,

Did u activate the condition table?

Regards,

Mani

[former_member182378]

Shiva,

With your instructions "Utilities" what shall happen?

Please explain.

[former_member182378]

Sachin,

Please check the field name of this "new" field (REGION) used in the condition table.

Then check in the sales order (tables VBAK, VBAP, VBEP) is this field present and what is the value of this field.

If the field name in the condition table and in the standard sales order tables match; and if there is a value for this field in your sales order, then the value should populate in your button "Analysis".

(as all the other fields of this condition type are populating).

FYI: I searched the Field catalogue, I found one field REGIO with description REGION, but this field does not exist in either of the three sales tables!

So please check this point.

Added: Saw your (last) screenshot with the field name of Region. Field name is REGIO

This field does not exist in tables related to Sales orders (VBAK, VBAP, VBEP).

Thus if your are looking at a sales order, this condition table shall not be "valid" (or picked up).

Note: At billing, at header level (VBRK), the field REGIO exists.

So you can have "redetermine pricing" (pricing type e.g. = B) at billing level.

If you want this condition table to be "valid" (or triggered or picked up).

Message was edited by: T W

[former_member182378]

Pitabash,

Your below comment is interesting

According to your screen shot it shows that it is a Discount condition .

Especially when in the pricing procedure screenshot there is no "Description" column (of condition type). Could you please comment on how you concluded that this is a discount condition?

It might have been a surcharge condition too!

[former_member182378]

Sachin,

In your pricing procedure screenshot, there are multiple requirements as 0!

Is 0 one of the routines?

Can you press F4, in the field requirement and then paste the code here?

Side comment: Strange to see "so many" zeros, in fields requirement, alt cal type, alt bas typ!

What are all these for?

[Former Member]

Hi T W,

It's according to the Accounting key "ERS" which is normally used in case of discount conditions.

Regards

Pitabash

[former_member182378]

Pitabash,

Thank you for your reply!

I too thought that but then when I looked in to pricing procedure RVAA01, surcharge condition types KP01, KP03 also have ERS as their Account key.