Loyalty Point condition 2901 inactive

Hi Guys
    when I configuration the loyalty manangement Point to Pay
    my conditon type 2901 display inactive,the detail informatin as follow
   someone knows how to solve it ? thank you

Similar Messages

2 condition types inactive -K - Inactive due to calculation basis/shipping

Hi Experts ,
I have 2 condition types inactive with the above message.
The things I have done to fix it..
Created fresh data and tried to run it.
used condition exclusion procedure.
Which worked in a previous scenario though.
Both condition types have similar calculation basis and teh condition records access is same but with different scales.
Awaiting your reponses.
rgds
Vineet_2006

vineet,
Reason of K - Inactive due to calculation basis/shipping is set for different reason explained in note 318775.
Check also point 1.2 from note 773034.
Above information will solve the query.
regards, david

Loyalty points are stored in which entity?

Hi,
I need to integrate Siebel's loyalty management with ATG and for That I need to know What is the data that flows from Siebel to ATG for loyalty functionality.
So I need to know below things-
In which entity loyalty/reward points are stored in Siebel or Where exactly is the loyalty points in Siebel?
Regards,
Prateek

There are several tables that hold variant info .. you can find these in SE11 / SE16 looking for VARI* e.g. VARID Variant directory, VARIT Variant texts -> but most of the time you should go through SAP function modules to read the contents of these e.g. RS_VARIANT_CONTENTS, as some of the data is held in INDX-type tables that you won't want to decode yourself...
Jonathan

Help with Java covert 5 loyalty points into 1 credit code.

Can u please provide the code so that:
Loyalty points can be converted into credits (5 loyalty points = 1 credit)
so far i have done....
public void ConvertPoints (int cr, int loy)
erm, these are my fields in the class
public class Loyalty
     private static int currentId = 2000;
private int cardId;
private String name;
private int rating;
private int credits;
private String centre;
public int loyalty;
my constructor:
public Loyalty (String nam, int rat, int cred,String cen, int loyalty)
name = nam;
rating = rat;
credits = 30;
cardId = currentId++;
centre = cen;
loyalty = 20;
Can u pleaseeeeee provide me the code to:
Loyalty points can be converted into credits (5 loyalty points = 1 credit)
thxsss help appreciated x

public class foo {
private int loyalty, credit;
public foo() {}
public int convertLoyaltyToCredits() {
    int credits = loyalty / 5;
    credit += credits;
    loyalty -= 5 * credit;
    return credit;

Loyalty points

Hi ,
I need a small inofrimation about loyalty points features in atg.do we have any loyalty points fetarures available in CRS? if not could you please tell some idea about how to implement this features?
Thanks,
Pveedu
l

Hi pveedu1
i think we don need any customization in OrderPriceEngine. Instead, While calling the CommitOrderFormHandler.commitOrder method write your logic there. Means assign some loyalty point for profile based on the order total. By this we can add loyalty point to the user.
Another Task is create a PaymentGroup called loyaltyPoint like Credit Card by that the user can use this points for the next purchase.
For Creating new http://docs.oracle.com/cd/E26180_01/Platform.94/ATGCommProgGuide/html/s1008extendingthepaymentprocesstosupp01.html refer this.
Regards
Kumaresh Babu A

Loyalty points program

Hi ,
How loyalty points program done in crm distributed through third party.
Answers will be rewarded.
Thanks & Regards,
Nandakumar

Loyalty points resolved.....

Condition is inactive

Hi,
while creating sales doc Condition type VPRS is not taking data from MM in the condition tab.
once i click on the details it shows condition is inactive due to formulae(x) was set.
where the inactive settings be done for condition type and how to activate condition type
regards
chidambaram

Hi,
Check the requirement routine assignment for the condition VPRS in transcation V/08 for your pricing procedure. Do you have your own routine assigned.
Regards,
Murali

Sample Javacard 2.2.1 Electronic wallet, Loyalty Points & StudentID applet

Hi All,
After nine months of researching and developing a java card applet and terminal side interface for my final year university project I was frustrated with the lack of sample code and tutorials available online.
My applet is aimed at students as an id card containing a student id, all the features of an electronic wallet, loyalty point system protected by a pin number. Pin is changeable.
The terminal interaction or host side application that communicates with this applet can be found in this forum under the heading "Sample Smartcardio (Host side) applet interaction application".
As I have no finished my project I would like to share it with anyone that would like to see it.
While I would love to write a tutorial I simply do not have the time however below is the applet I used in my project, I how for anyone that has read through java sun's tutorials this will be a help:
package account;
import javacard.framework.APDU;
import javacard.framework.APDUException;
import javacard.framework.ISO7816;
import javacard.framework.Applet;
import javacard.framework.ISOException;
import javacard.framework.OwnerPIN;
import javacard.framework.TransactionException;
import javacard.framework.Util;
* @Raymond_Garrett
* DT 354-4
*Applet ID 41 63 63 6F 75 6E 74 41 70 70 6C 65 74
public class AccountApplet extends Applet {
     // codes of CLA byte in the command APDUs
     final static byte ACCOUNT_CLA = (byte)0xA0;
     // codes of INS byte in the command APDUs
     final static byte VERIFY_INS = (byte) 0x20;
     final static byte CREDIT_INS = (byte) 0x30;
     final static byte DEBIT_INS = (byte) 0x40;
     final static byte GET_LOYALTYPOINTS_BALANCE_INS = (byte) 0x45;
     final static byte CREDIT_LOYALTYPOINTS_INS = (byte) 0x47;
     final static byte GET_BALANCE_INS = (byte) 0x50;
     final static byte UPDATE_PIN_INS = (byte) 0x60;
     final static byte ADMIN_RESET_INS = (byte) 0x70;
     final static byte PIN_TRIES_REMAINING_INS = (byte) 0x80;
     final static byte STUDENT_NUMBER_INS = (byte) 0x90;
     // maximum Account balance
     final static short MAX_BALANCE = 10000;
     // maximum transaction amount
     final static short MAX_TRANSACTION_AMOUNT = 5000;
     // maximum number of incorrect tries before the
     // PIN is blocked
     //Changed to 4, as a safe guard all. All tests, messages and checks will use 3
     final static byte PIN_TRY_LIMIT =(byte)0x04;
     // maximum size PIN
     final static byte MAX_PIN_SIZE =(byte)0x08;
     // Applet-specific status words:
     final static short SW_NO_ERROR = (short) 0x9000;
     final static short SW_VERIFICATION_FAILED = 0x6300;
     final static short SW_PIN_VERIFICATION_REQUIRED = 0x6301;
     final static short SW_INVALID_TRANSACTION_AMOUNT = 0x6E83;
     final static short SW_EXCEED_MAXIMUM_BALANCE = 0x6E84;
     final static short SW_NEGATIVE_BALANCE = 0x6E85;
     final static short SW_PIN_TO_LONG = 0x6E86;
     final static short SW_PIN_TO_SHORT = 0x6E87;
//     Student number (Ascii)d05106012 - (Hex)44 30 35 31 30 36 30 31 32
     private static byte[] STUDENT_NUMBER_ARRAY = {(byte)0x44, (byte)0x30, (byte)0x35, (byte)0x31, (byte)0x30, (byte)0x36, (byte)0x30, (byte)0x31, (byte)0x32};
     // instance variables declaration
     OwnerPIN pin;
     short balance = 1000; // Starting balance of decimal 1000 is 3E8 in hex
     short loyaltyPoints = 0; //Loyalty points
     // 1 Loyalty point awarded for every 100 cent spent.
      * install method
     public static void install(byte[] bArray, short bOffset, byte bLength) {
          // GP-compliant JavaCard applet registration
          new AccountApplet(bArray, (short) (bOffset + 1), bArray[bOffset]);
      * Constructor
      * @param bArray
      * @param bOffset
      * @param bLength
     private AccountApplet(byte[] bArray, short bOffset, byte bLength){
          pin = new OwnerPIN(PIN_TRY_LIMIT, MAX_PIN_SIZE);
          // bArray contains the default PIN initialization value (12345)
          bArray[0] = 01;
          bArray[1] = 02;
          bArray[2] = 03;
          bArray[3] = 04;
          bArray[4] = 05;
          bOffset = 0;
          bLength = 5;
          pin.update(bArray, bOffset, bLength);
          // register the applet instance with the JCRE
          register();
     } // end of the constructor
      * Boolean is selected
     public boolean select() {
          // the applet declines to be selected
          // if the pin is blocked
          if (pin.getTriesRemaining() == 0)
               return false;
          return true;
     } // end of select method
      * deselect
     public void deselect() {
          // reset the pin
          pin.reset();
      * Key method the gets the APDU reads the INS and calls the appropiate method
      * Process APDUs
      * @param apdu
     public void process(APDU apdu) {
          // APDU object carries a byte array (buffer) to
          // transfer incoming and outgoing APDU header
          // and data bytes between the card and the host
          // at this point, only the first five bytes
          // [CLA, INS, P1, P2, P3] are available in
          // the APDU buffer
          byte[] buffer = apdu.getBuffer();
          // return if the APDU is the applet SELECT command
          if (selectingApplet())
               return;
          // verify the CLA byte
          if (buffer[ISO7816.OFFSET_CLA] != ACCOUNT_CLA)
               ISOException.throwIt(ISO7816.SW_CLA_NOT_SUPPORTED);
          // check the INS byte to decide which service method to call
          switch (buffer[ISO7816.OFFSET_INS]) {
          case GET_BALANCE_INS:                    getBalance(apdu);                return;
          case DEBIT_INS:                              debit(apdu);                       return;
          case CREDIT_INS:                         credit(apdu);                     return;
          case VERIFY_INS:                         verify(apdu);                    return;
          case UPDATE_PIN_INS:                    updatePin(apdu);               return;
          case ADMIN_RESET_INS:                    adminRest();                    return;
          case PIN_TRIES_REMAINING_INS:           getPinTriesRemaining(apdu); return;
          case STUDENT_NUMBER_INS:                getStudentNumber(apdu);      return;
          case GET_LOYALTYPOINTS_BALANCE_INS:     getLoyaltyPoints(apdu);      return;
          case CREDIT_LOYALTYPOINTS_INS:      creditLoyaltyPoints(apdu);      return;
          default:                    ISOException.throwIt
          (ISO7816.SW_INS_NOT_SUPPORTED);
     } // end of process method
      * verify then
      * withdraw money from the Account balance
      * @param apdu
     private void debit(APDU apdu) {
          // verify authentication
          if (!pin.isValidated()){
               ISOException.throwIt(SW_PIN_VERIFICATION_REQUIRED);
          byte[] buffer = apdu.getBuffer();
          // get the number of bytes in the
          // data field of the command APDU
          byte numBytes = buffer[ISO7816.OFFSET_LC];
          //receive data
          //data is read into apdu buffer
          //at offset ISO7816.OFFSET_CDATA
          byte byteRead = (byte)(apdu.setIncomingAndReceive());
          short shortAmount = 0;
          if (numBytes == 2){
               shortAmount = (short) Util.getShort(buffer, ISO7816.OFFSET_CDATA);
          else if (numBytes == 1) {
               shortAmount = (short) buffer[ISO7816.OFFSET_CDATA];
          // check the debit amount
          if (( shortAmount > MAX_TRANSACTION_AMOUNT)     || ( shortAmount < 0 )) {
               ISOException.throwIt(SW_INVALID_TRANSACTION_AMOUNT);
          // check the new balance
          if ((short)( balance - shortAmount) < 0) {
               ISOException.throwIt(SW_NEGATIVE_BALANCE);
          // debit the amount
          balance = (short)(balance - shortAmount);
          //Add loyalty points
          loyaltyPoints = (short) (loyaltyPoints + (short)(shortAmount/100));
          return;
     }          // end of debit method


Code continued>>>>>>>>
      * Verify then
      * add money (credit) to the Account balance
      * @param apdu
     private void credit(APDU apdu) {
          // verify authentication
          if (!pin.isValidated()){
               ISOException.throwIt(SW_PIN_VERIFICATION_REQUIRED);
          byte[] buffer = apdu.getBuffer();
          // get the number of bytes in the
          // data field of the command APDU
          byte numBytes = buffer[ISO7816.OFFSET_LC];
          //receive data
          //data is read into apdu buffer
          //at offset ISO7816.OFFSET_CDATA
          byte byteRead = (byte)(apdu.setIncomingAndReceive());
          short shortAmount = 0;
          if (numBytes == 2){
               shortAmount = (short) Util.getShort(buffer, ISO7816.OFFSET_CDATA);
          else if (numBytes == 1) {
               shortAmount = (short) buffer[ISO7816.OFFSET_CDATA];
          // check the credit amount
          if (( shortAmount > MAX_TRANSACTION_AMOUNT)     || ( shortAmount < 0 )) {
               ISOException.throwIt(SW_INVALID_TRANSACTION_AMOUNT);
          // check the new balance
          if ((short)( balance + shortAmount) > MAX_BALANCE) {
               ISOException.throwIt(SW_EXCEED_MAXIMUM_BALANCE);
          // credit the amount
          balance = (short)(balance + shortAmount);
          return;
     }                                                       // end of deposit method
      * Verify then
      * Update/change pin
      * byte[] bArray is the pin
      * short bOffset is the position in the array the pin starts in the bArray
      * byte bLength is the lenght of the pin
      * @param apdu
     private void updatePin(APDU apdu) {
          //     byte[] bArray, short bOffset, byte bLength){
          //           First check the original pin
          //          verify authentication
          if (! pin.isValidated())
               ISOException.throwIt(SW_PIN_VERIFICATION_REQUIRED);
          byte[] buffer = apdu.getBuffer();
          // get the number of bytes in the
          // data field of the command APDU -- OFFSET_LC = positon 4
          byte numBytes = buffer[ISO7816.OFFSET_LC];
          // recieve data
          // data are read into the apdu buffer
          // at the offset ISO7816.OFFSET_CDATA
          byte byteRead = (byte)(apdu.setIncomingAndReceive());
          // error if the number of data bytes
          // read does not match the number in the Lc byte
          if (byteRead != numBytes) {
               ISOException.throwIt(ISO7816.SW_WRONG_LENGTH);
          if ( numBytes > 8 )
               ISOException.throwIt(SW_PIN_TO_LONG);
          if ( numBytes < 4 )
               ISOException.throwIt(SW_PIN_TO_SHORT);
          short offset_cdata = 05;
          pin.update(buffer, offset_cdata, numBytes);
          pin.resetAndUnblock();
      * Admin method
      * Rest the pin attempts and unblock
      * @param apdu
     private void adminRest() {
          try {
               pin.resetAndUnblock();
          } catch (RuntimeException e) {
               // TODO Auto-generated catch block
          return;
      * Credit loyatly card pints in multiples of 100
      * @param apdu
     private void creditLoyaltyPoints(APDU apdu) {
          short creditAmount = (short) ((loyaltyPoints/ 100) * 100);
          balance = (short) (balance + creditAmount);
          loyaltyPoints = (short) (loyaltyPoints - creditAmount);
          return;
      * Get number of remaining pin tries
      * @param apdu
     private void getPinTriesRemaining(APDU apdu) {
          try {
               byte[] buffer = apdu.getBuffer();
               // inform the JCRE that the applet has data to return
               short le = apdu.setOutgoing();
               // set the actual number of the outgoing data bytes
               apdu.setOutgoingLength((byte)2);
               // write the PinTriesRemaining into the APDU buffer at the offset 0
               Util.setShort(buffer, (short)0, pin.getTriesRemaining());
               // send the 2-byte balance at the offset
               // 0 in the apdu buffer
               apdu.sendBytes((short)0, (short)2);
          } catch (APDUException e) {
               // TODO Auto-generated catch block
          } catch (TransactionException e) {
               // TODO Auto-generated catch block
          } catch (ArrayIndexOutOfBoundsException e) {
               // TODO Auto-generated catch block
          } catch (NullPointerException e) {
               // TODO Auto-generated catch block
     } // end of getPinTriesRemaining method
      * No verification needed
      * the method returns the Accounts balance
      * @param apdu
     private void getBalance(APDU apdu) {
          byte[] buffer = apdu.getBuffer();
          // inform the JCRE that the applet has data to return
          short le = apdu.setOutgoing();
          // set the actual number of the outgoing data bytes
          apdu.setOutgoingLength((byte)2);
          // write the balance into the APDU buffer at the offset 0
          Util.setShort(buffer, (short)0, (balance));
          // send the 2-byte balance at the offset
          // 0 in the apdu buffer
          apdu.sendBytes((short)0, (short)2);
      * No verification needed
      * the method returns the Accounts loyaltyPoints balance
      * @param apdu
     private void getLoyaltyPoints(APDU apdu){
          byte[] buffer = apdu.getBuffer();
          // inform the JCRE that the applet has data to return
          short le = apdu.setOutgoing();
          // set the actual number of the outgoing data bytes
          apdu.setOutgoingLength((byte)2);
          // write the loyaltyPoints balance into the APDU buffer at the offset 0
          Util.setShort(buffer, (short)0, (loyaltyPoints));
          // send the 2-byte loyaltyPoints balance at the offset
          // 0 in the apdu buffer
          apdu.sendBytes((short)0, (short)2);
      * No verification needed
      * the method returns the student number
      * @param apdu
     private void getStudentNumber(APDU apdu) {
          byte[] buffer = apdu.getBuffer();
          // inform the JCRE that the applet has data to return
          short le = apdu.setOutgoing();
          // set the actual number of the outgoing data bytes
          apdu.setOutgoingLength((byte)STUDENT_NUMBER_ARRAY.length);
          // write the balance into the APDU buffer at the offset 0
          apdu.sendBytesLong(STUDENT_NUMBER_ARRAY, (short)0, (short) STUDENT_NUMBER_ARRAY.length);
          //     Util.setShort(buffer, (short)0, STUDENT_NUMBER_ARRAY);
          // send the 2-byte balance at the offset
          // 0 in the apdu buffer
          try {
               apdu.sendBytes((short)0, (short)STUDENT_NUMBER_ARRAY.length);
          } catch (APDUException e) {
               // TODO Auto-generated catch block
     } // end of getBalance method
      * Verification method to verify the PIN
      * @param apdu
     private void verify(APDU apdu) {
          byte[] buffer = apdu.getBuffer();
          // receive the PIN data for validation.
          byte byteRead = (byte)(apdu.setIncomingAndReceive());
          // check pin
          // the PIN data is read into the APDU buffer
          // starting at the offset ISO7816.OFFSET_CDATA
          // the PIN data length = byteRead
          if (pin.check(buffer, ISO7816.OFFSET_CDATA,byteRead)
                    == false)
               ISOException.throwIt(SW_VERIFICATION_FAILED);
     } // end of verify method
} // end of class AccountEdited by: Raymond.garrett-Dublin on Jun 17, 2009 11:30 PM

All conditions are Inactive

Dear all,
In billing document all the condition are inactive the reason the system is displaying is "W" The document item is statistical.
There is only one line item in billing.
The billing is made with reference to order.
In order all the condition are active.
The pricing condition is entered manually since no condition records are maintained and it is marked as manual in pricing procedure as wel as at condition level.
In billing all the conditions are unique i.e no condition is inserted twice.
Regards
Vipin

Dear Sandip,
Thank you for the reply the pricing is already activated at item category level.
Secondly we do have previous billing document with same material, customer and sales doc. type released to accounting.
For convenience I am posting the condition type used in billing
        Class     Statistical
ZPR0     B
ZHDI     A     A
ZCUD     A     X
JEXP     A     X
ZEDC     A     X
ZHCE     A     X
ZCCE     A     X
ZCHC     A     X
ZEX1     A
ZEX2     A
ZEX3     A
JLST     D
VPRS     B     X
All the above condition are inactive in billing and active in order
Regards
Vipin

VA01 has Condition is Inactive for my PR00

Hello all,
I created my Sales Order. When I go Item Condition I get the right value at Amount & Condition Value from my PR00.
If I click on Analysis and check my PR00, I have: Condition Record has been found.
However the 1º column (Display Inactive Conditions) from my PR00 is:
- Amber traffic light: CONDITION IS INACTIVE (KINAK not equal to 'X' and ' ').
I do not know what is KINAK!!!!
When I create the Billing and go to Item Condition I have for this PR00:
- Display Inactive Conditions = Green traffic light: CONDITION IS ACTIVE (KINAK = ' ')
What should I do to have, in my Sales Order, my PR00 = CONDITION IS ACTIVE (green traffic light at display inactive conditions collumn)?
Many thanks & Regards,
Barbara

Hi Barbara
You may check upon the Condition exclusion record , may be the reason to show the inactive condition.
I am not sure whether you are using ECC 6 if yes then you may also check of
Tab Process Status in condition record maintence.
This new functionality allows precheck of condition records prior billing
Hope this solves your problem
regards
Saurabh

Condition record Inactive

Dear All
I have an access sequence maintained say Customer/Material and I have maintained two different condtion records with same customer number and material number.
What system is doing is that it is making one of the condition record inactive and other one active. My requirement is that both of them should be active as these are two separate component of the cost.
What can be the way to achieve the same
Cheers!!
Gaurav

Go to V/06, select any one of those condition type and execute. There change the value for the field Condition Class other than B.
thanks
G. Lakshmipathi

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]

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

Statistic Condition Type inactive when duplicated

Hi gurus,
I wonder if there's any way to make a statistic condition type become inactive when the user inserts another equal one.
Example:
Here is my procedure: ZP0001 with this condition type ZC01 set statistic.
If I create a new sales order and I insert this condition in the procedure twice, the system does NOT deactivate any of them. It just let them occur at the same time.
If I go like this with a non statistic condition type, then the system deactivate all duplicated types and only remains the last one inserted.
Do you know if this behaviour is possible for statistic condition types in any way?
Thanks in advance,
John

Hi,
a statistical condition type can not be inactive because it is not taken into account in the calculation per definition as statistical.
One more sentence to clarify to the sentence before. It will be inactive but still displayed - as this is the nature of a statistical condition.
So far so good. But I know exactly what your problem is, when your statistical condition type is present twice you would like to surpress the earlier record.
We had a similar requirment once. We had two different statistical condition types which were displayed at the same time.
The requirement was to only display one of the two condition types. When A was present B should not be shown. I tried with condition exclusion but it did not work for statsitical conditions (as they can not be set inactive...). But it worked very good with a pricing requirement we created ourselves.
Good Luck.

VPRS Condition is inactive

Hi,
in my sales order for a line item, my vprs condition is not being calculated. I have maintained standard price in material master but the cost is not inlcuded in the line item of sales order.
when i see in the item pricing for the VPRS condition type in the conditon detail, the condition is marked as inactive with description "inactive via formulae of incorrect".
I have aslo seen one thing in material master. when i set the price control indicator to S, the standard price field becomes grey and when i set the pricing indicator to V, the moving price indicator becomes grey ??
how to make the condition VPRS active???
regards
sachin

Hi,
Please check whether the Plant number is appearing in the 'Plant' field in the Shipping tab at line item level of the Sales order.
I think this should work.
Reward if helpful.
Manjunath.

Loyalty Point condition 2901 inactive

Similar Messages

Maybe you are looking for