Copying Rules & Access Sequence

Dear Experts,
I need to know how can I force the Purchase order to not adopt the conditions from the last PO or even the info record.
I also need to know how can I make the "Info Update" Indicator not checked by default
Best reagards

hi,
The info update indicator is controlled via EVO paramters...
check the settings here:
SPRO >> MM >> Purchasing >> Environment >> default value for buyers...
regards
Priyanka.P

Similar Messages

Copying Custom Access Sequences to CRM from R/3

Here is the scenario we're working with:
Use quotes in CRM which are then released to orders in R/3. Would like to use pricing procedures to default in fixed prices for certain materials. Have everything working fine in R/3. I am following the process outlined in the Replication guide.
We created a new access sequence for pricing use SalesOrg/DistChan/Division/Batch. Created table A991 which has entries stored.
Running DNL_CUST_CNDALL does not bring the access sequence across. Tried defining my own customizing object specifying the new table and I get the following error in SMW01:
<b>Target table CNCCRMPRCUS991 is not actively available</b>
Is there a certain order I was supposed to do this in?

Hi Raghu,
Please refer the Best Practices document for replicating BP's from R/3 to CRM. Please have a look the following document for your information.
http://help.sap.com/bp_crmv340/CRM_DE/index.htm
under Technical Information->Building Block Library->B09: CRM Replication. page no.45 onwards.
Reward if it helps.
Best Regards,
Johnny.

Copy rule

Hi
What is "copy rule" in condition record? How to use it.
Thanks in advance

Copy rule for conditions determines:
1. Which source condition type can be copied to a target condition type.
2. Which table in the source condition type can be copied to which table in target condition type.
3. Requirements and limitations.
Source and target field serves as copy strategy, standard system only predefined two: from customer to customer(s), from material to material(s).
As an example, you want to define a rule to make it possible to copy PR00 (rarely happens): Go to pricing - pricing control copy control for conditions - Copying rule for condition types VB(C. Then add new entry: source condition type PR00 and target PR00.
Then we go to VB(B to set the rule which table in access sequence of PR00 can be copied. since access sequence is pr02 containing tables 304,305, 306. We pick from table 305 to 305, field KUNNR to KUNNR, so that condition record 305 can be copied form a customer to another customer(s). We can set default rule for the table as well.
This is not in real business, only a logic for you to understand..

When defining copy rules, only one source field allowed

Our users have requested the facility to allow them to copy pricing condition records when in in VK12 transaction. But when configuring the copy rules, we have come across the following problem:
When configuring copying rules for copying pricing condition records,
there is no possibility to use more than one source/target fields.
In our example, the condition table created for a certain pricing
access sequence contains keys such as Sales Organization, Sold-to Party
"and" Product Hierarchies level 1 to level 9 (e.g. PH1 - PH9) .
In the condition table definition, fields PH1 to PH9, although key
fields, are also defined as footer fields. This means that per sales
organization and sold-to party, we can create more than one condition
record based on different combinations of PH1 to PH9.
However when setting up copy rules for conditions in SPRO (SD -
Pricing Control - Copy Control for Conditions) to allow our users to copy the condition records, for a given Source /
Target table, the standard selection screen only allows us to define one Source / Target field.
In our case, this is not helpful. The configurator should be allowed
to select more than one source field (i.e. PH1 and PH2 and ..... PH9). At this moment,
we can only select as source field PH1 or PH2 or PH3., etc..
Steps for the Reconstruction:
- Run Spro.
- Select SD --> Pricing --> Pricing control --> Copy control for conditions -- > Copying rule for conditions
- Select 'New Entries'. Selection screen is displayed. The issue is that in this selection screen, the configurator is allowed to select only one source field. He should be allowed to select multiple fields.
Can you help us with this problem please?
Your help is much appreciated!
Edited by: C. Hassink on Feb 2, 2008 3:50 PM
Edited by: C. Hassink on Feb 2, 2008 3:52 PM
Edited by: C. Hassink on Feb 2, 2008 3:53 PM
Edited by: C. Hassink on Feb 2, 2008 3:55 PM
Edited by: C. Hassink on Feb 2, 2008 3:56 PM

Hi Ralph,
I don't like that methode. Importing the same transport 15 times, each time changing the source-system mapping and making sure, that source-system gets the changes seems to be a huge source of errors, which will be hard to find.
What do you think of the following idea to solve the issue a totally different way:
All transfer-rules directly connected to the source-systems are stripped of all Coding, so there is a plain 1 by 1 transformation including 0logsys.
The InfoSources attached all lead to one ODS-Object, which has the only purpose to collect the data from the source-system without any transformation. So some fields a filled by a system and other fields maybe not.
The coding specific for source-systems is moved to transfer- / update-rules from that ODS-Object to the original ODS-Objects / Cubes and the "collecting" ODS-Object is emptied after every loading process.
This will result in a single point of change. It will be quite a huge program (maybe in startroutine) but it's the one and only point, where changes and corrections have to be made.
Regards
Robert

How to create the Access sequence for the Vendor+material+plant combination

Hi all
Please let me know How to create the Access sequence for the Vendormaterialplant combination..
Whats the use? What its effect in purhcase and taxe..
brief me please

Hi,
you are asked to maintain the access sequence for the tax condition for which you are putting 7.5%.
goto OBQ1 or img..financial accounting new...global settings.... taxes on sales and purchases ......basic settings.....
find the tax condition type. see in it which access sequence is attached.
if there is none then use JTAX used for taxes in India.
or you can create the similar one for your.
to create the same goto OBQ2.
new entry or copy JTAX.
and assign the access sequence to condition type.
this will resolve your problem if you just need to assign the access sequence.
regards,
Adwait Bachuwar

SolMan 4.0: Support Team determination via Access Sequence not working

Hi,
from all the documentation I've read I got the following understanding for automatically determination of Support Team via Access Sequence (well, for one possibillity at least):
- Maintain Sold-to-Party in IBase IB52, especially country attribute. DONE
- Maintain Organizational Structure in PPOMA_CRM and create Org. Units, Business Partner No. get assigned automatically. DONE
- The Organizational Unit "Support Team" has the same country attribute as the Sold-to-Party and was marked "Obj. Permitted in Determination". DONE
- In IMG under SolMan -> Sc.-Specific Settings -> Partner Det. Proc. -> Def. Partner Det. Procedure select Procedure "SLFN0001" -> Partner Functions in Procedure -> Select "Support Team" -> Details, in block "Partner Determination" under "Access Sequence" select "Organizational data: Support Team by org. model". DONE
If I now create a support message in a satellite system the Support-Team will NOT be assigned. Instead if I have a look into transaction data of the message under tab "Actions" there is an entry "When message is created, find support team responsible" with processing parameters RULE AC13200137, PARTNER_FCT SLFN0003.
This makes absolutely no sense to me, why is the determination rule 13200137 used (which contains no entries at the moment) instead of the assigned Access Sequence?
Am I missing something?
Regards,
Marco Kipka

Hi,
no hint for solving the problem?
This is getting quite urgent, since I'm working at a customers site and try to implement the describted scenario.
Regards,
Marco

Access Sequence for Purchase Orders

Hi,
When copying Access Sequence 0001 to my new Access Seq: ZPR1, I am hitting the below error.
The field assignment has not yet been made
Message no. VK 376
Diagnosis
Field assignment has not yet been carried out.
System Response
When using this access sequence, the system can never find a record for this access (sequential number 11 table 025)
Procedure
Branch to field level and make the field assignment.
Pls advise the cause.
Thanks,
Pri

well it shouldnt be an error message it should be a warning message
acknowledge the message and then selcet the row of the condition table in the acess sequnece and then click on the folder field s and do this for all the condition tables in the access sequence and then save
i will again say it is just an warning messgae so as to inform you that while including a new table u sholud select the row and then click on the field s folder this makes an interal assignement
do this and your problem will be solved 101%

New Access Sequence

Dear Team,
I have created New Access Sequence ZJTX copy of JTAX. As below
1. Query-1
No.               table               Description
10     363     Plant/Vendor/Material
20     900     Plant/Tax Code
30     910     Plant/Vendor/Matl Group
50     930     Plant/Vendor
Having exclusive indicator to 10, 20 & 30.
But when I maintain condition in FV11 like JVRD & create Purchase order. It DOES NOT show me taxes.
2. Query-2
I am not able to Create combination Plant/vendor/country/region. For Region Doc field is Empty. Status Indicator is Red.
Pls suggest
Thanks
Tushar

Dear TEam,
I have created new Condition Table 960: tax code/plant/vendor/mateiral
1. When I maintain any table created by me in Access Sequence ZJTX, warning message comes
The field assignment has not yet been made
Message no. VK376
Diagnosis
Field assignment has not yet been carried out.
System Response
When using this access sequence, the system can never find a record for this access (sequential number 04 table 960)
Procedure
Branch to field level and make the field assignment.
Pls suggest urgently whats wrong
Regards

Access Sequence for PO output

Hi experts,
I have defined new PO output type in NACE by copying existing one.
I have created New Condition Table for PO output (in SPRO).
Now, i want to create new access sequence. But, i am facing following problems
1. If i try to create new access sequence by copying existing one , i am not able to add Newly defined condition table.
2. if i try to create new access sequence without copying existing one , i am not able to enter access i.e. 10 ,20 , 30, 40 .... for access sequence.
Also , how to link this new access sequence to newly defined Condition table?
Please, guide me to resolve it
Regards,
rahul
Edited by: RahulNsk on May 9, 2009 9:34 AM

David,
I can't answer your question directly but I can propose an alternative:
If you are looking for another field to trigger output determination, you may want to consider having an ABAP developer create a custom requirement for that output type. Requirements can make simple validation checks and if it passes (sysubrc = 0) then the output is proposed, if not, then output is not proposed.
Create requirement @ Materials Management > Purchasing > Messages > Output Control > Maintain Requirements for Message Control
Assign requirement to output type @ Materials Management > Purchasing > Messages > Output Control > Message Determination Schemas > Define Message Schema for Purchase Order.
I hope this helps

New Access Sequence for Tax based on material Group

Hello All,
Our requirement is that we tax our employees on apparel only if the value is greater than $50.00.
To achieve this, we created a new tax condition table (953 which is copied from 053) and assigned it to access 09 in the access sequence ZTX1 (created w/ref from TAXJ). We added material group (MATKL) to the condition table and selected exclusion indicator for the access.
We created the condition record in FV11.
When we created the sales order, the new access sequence (09) is not being accessed. It gives a message "Access not made (initialized field)" Message 102(VE).
Please advise if we are missing something.
Thanks,
Leela

Hi Leela,
Are you creating sales order in the same system like
You have created table in Development system in same system your are creating sales order
If you are creating here you just go to V/07 transaction then slect your access sequence go in to the tables detail screen here you select your table 953 then click on fields here you check all the fields are available correctly or not then save the changes.
Now try
or
You transported these confugaration to other system like Quality or Production here and you are creating the sales order,
If you are creating here you need to create condition table again then try.
I hope it will help you,
Regards,
Murali.

Purpose of Access sequence in text determination procedure?

Dear all,
I can get my text id's at sales document header/item level by simply assigning my defined text id to the text determination procedure.
now, what is the need for having an access sequence where a text abject and text id is maintained??
Thanks and regards
KV

Hi,
Define Access Sequences For Determining Texts
In this IMG activity, you define the access sequences which the SAP System uses to determine the texts for a text object.
Afterwards, you specify an access sequence for the text search in the determination procedure for every text type.
You only define access sequences for sales and distribution documents, not for customer master records.
With an access sequence, you define the sequence and the requirements of the search used by the SAP System to find a text.
This allows you, for example, to have the system check whether a text exists in the customer language. If this is not the case, then a text in the sales organisation language can be searched for. If this is also unsuccessful, you can have the system carry out the search using English as the fixed value.
To do this, you make the following specifications for every access sequence:
acc. no (access number)
With the access number, you define the sequence in which the text objects of an access sequence should be read. The element with the lowest access number is read first. If an appropriate text is found, the search is ended. Otherwise, the SAP System checks the element with the next number up.
Text object
Here, you define which text objects should be checked by the SAP System for an access sequence.
In the standard SAP R/3 System, for example, in the access sequence 0001 for the text object sales document header is defined, that the SAP System first searches for a form header text in the preceding document (text object VBBK) and afterwards for a sales note in the customer master record (text object KNVV).
ID (text type)
Here, you define which text type is to be read from the specified text object.
It is recommended to select the same text type for the text to be copied. For example, the text for the form header in the customer master record (text type 0001) should be copied into the text for form header of a sales document (text type 0001).
kapil

Access Sequence Field not recognized in the Account Determination

Hi All,
we have created a new table for the account determination access sequence we are using as default.
the new table contains the field MVGR2 (VBAP) which we added to the KOMPCV structure as ZZMVGR2.
this goes fine in the sales order, however this is no longer recognized during billing. the field has no value in the Account determination analysis, hence there is no GL account determined for that.
can anyone help?

My guess is: you will have to modify the copy control routine, and populate the value of the new field accordingly.
This routine needs to be assigned to the item category in copy control configuration (VTFL).
Needless to say, the existing routine should be copied and then modified.
Regards,
Aroop

Related to condition types and access sequence

Dear all,
i want to know abt one scenario, m using a pricing procedure with my service PO: ZVSTOT, in this Procedure, 12 condition types are there, during searching i found tat 3- 4 condition are are using different different access sequence, so i want to know tat in what procedure, we do it, what is use of it.?
plz reply me.

Hi Nisha,
Prcing procedure configured in your service PO PO: ZVSTOT, Based on this pricing procedure system adopted the condition type in PO.
Please go through this below link to better understanding the MM-Pricing procedure
http://it.toolbox.com/wiki/index.php/Pricing_Determination_Process_-_MM
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
CONDITIONS OR PRICING PROCEDURE or PRICE DETERMINATION PROCESS
We deal with the Pricing Procedure for vendors.
PB00 Gross Price (info record, contract, scheduled Agreement)
PBXX Gross Price (PO)
FRA1 Freight
RA00 Discount on net
RA01 Discount on Gross
ZA00 Surcharge on net
SKT0 Surcharge / discount
ZPB0 Rebates
MWVS Input Tax
MWAS Output Tax
BASB Base Amount
RM0000 Calculation Schema or Pricing Procedure
(PB00 & PBXX)
RM0002 Calculation Schema or Pricing Procedure
(PB00)
PB00 --> AB00
Copy the Standard one and create new one (ours)
RM0000 contains all the condition types
Pricing Procedure (PP)
We define the pricing procedure to define condition supplement for the material price. The condition supplement specifies the discount, surcharge, freight etc that we want a system every time to access material price condition records.
The total value of the material is calculated or based on all addition and subtraction i.e. discounts, surcharge, tax freight etc
Condition Table
It is a table, which defines the structure of condition record key.
Condition Record
It is a data record used to store conditions or condition supplements, i.e. condition like, discount, freight, and surcharge, Tax etc.
Condition Type
It is used for different functions. In Pricing the condition types leads you to differentiate different types of discounts, in output determination, batch determination, difference between two output types, such as delivery note or order confirmation, between different strategy types
Access Sequence
It specifies the order in which system searches or access the condition records from condition table
Difference between PB00 & PBXX
1. Condition maintained in PB00 is time dependent whereas PBXX is time independent.
2. Condition type PB00 u2013 used for IR, RFQ, Contract, Schedule Agreement
Condition type PBXX u2013 used for PO.
Calculation Schema
The main function of calculation schema is to provide framework of steps for the price determination process to specify the discounts, surcharge, freight rebate etc.
It also determines the sequence of conditions that are to be followed and in which sequence.
Schema Group Vendor
The main function of it is to identify or to pick the right process and conditions for a particular vendor.
Schema Group Purchasing Organization
Key that determines which calculation schema (pricing procedure) is to be used in purchasing documents assigned to the relevant purchasing organization.
Schema Group
It allows to group together the purchasing organizations, which uses the same calculation schema.
Steps: -
1. Create Access sequence
2. Create condition types
3. Create pricing procedure or calculation schema
4. Link pricing procedure & access sequence to condition type
5. Create schema group for vendor
6. Create schema group for purchase organization
7. Assign schema group vendor-to-vendor master record in purchasing data view
8. Assign schema group purchase organization to our purchase organization
9. In inforecord purchase organization data enter condition types and pricing or calculation procedure
CUSTOMIZE SETTINGS: -
SPRO > IMG>MM>PUR>Conditions -->Define price determination Process
1. Define access sequence
2. Define Condition type
3. Define cal. Schema
4. Define schema group
o Schema group vendor
o Schema group purchasing group
5. Assignment of schema group to PUR org
6. Define schema determination à determine cal schema for standard PO.
With Thanks,
Thiru

Partner Determination Procedure-access sequence

Dear Gurus,
My requirement is support team determination when message is created.I maintained the Rule 13200137 in PFAC_RESPO.
In this below path in procedure SLFN0001 against partner function procedure of funcions SLFN0003 SUPPORT TEAM (CRM).IN THE PARNER DETERMINATION TAB acces sequence and Determination Time in Partner Determination are empty.
what values should i maintain here so that support team determination will happen as per the rule 13200137
SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure -> Define Partner Determination Procedure.
plz guide me

Hey SAPuser,
You can use access sequence Organization data: Service Team using product or rule....
If this does not work out, then you need to work out some other access sequnce which starts with something like: Organization data: ........
Reward for usefull post...
Regards,
Anand

Requirements in access sequence

Hi Gurus.
     can anyone plz tell me with an example why requirement is used in
     access sequence.
Thanks & Regards.

Hi Sujith,
Requirements is a set of rules/ formula, which has to met before the access is used.
Requirements in access sequence is used to reduce the time taken for retrival of data.
Eg.
If the access is applicable only for export business, requirement 8 can be used. This requirement checks whether the order is export business. If yes then access is used, if no the system goes to next access.
reward if useful
Reagrds
S Pradeep
Message was edited by:
        Pradeep S

Copying Rules & Access Sequence

Similar Messages

Maybe you are looking for