Purchase Requisition Release Strategy based on Order # Range

Question:
Has anyone configured the PREQ release strategy based on order # range?
I've got a few different order # ranges which need to go to different people for approval.
Example, Internal Order # 11******* goes to John Doe
Internal Order # 12******* goes to Susan Smith
I can't seem to enter a number range in the CEBAN-AUFNR characteristic. And there are way to many order #s to add them to the characteristic on an ad-hoc basis.
Any ideas?
Answer:
What I'd like to know is if anyone out there has done approval based on Order #s and if so, how, and has anyone had any expereince using the user exit/enhancement "M06B0001/EXIT_SAPLEBNF_001"
Dave
Answer:
Hi Dave,
The User Exit that you have mentioned was not relating to your specific requirement. In fact, this User Exit is used with the Workflow defined in the Release Strategy. Besides, why couldn't you use CEBAN-AUFNR as part of your authorization objects? What was the error message have you encountered? When assigning the value to this release characteristics via Transaction CT04, you have to set up the number range rather than the specific number. Let me know again if this works.
Cheers,
HT
Answer:
It's a 12 character "CHAR" field and the documentation tells me I can't put in number ranges......
I'll try again tomorrow.
Answer:
Multiple-values indicator refers to a reference characteristic
Message no. C1 125
Diagnosis
Characteristic PREQ_RELEASE_ORDER refers to field AUFNR in table CEBAN.
Usually, such a field contains exactly one value. This contradicts the
multiple-values indicator.
Object characteristics that refer to the structure SDCOM and are needed
in variant configuration for pricing are an exception. Characteristics
that refer to this structure must have multiple values.
Procedure
Check whether you really need this indicator.
Answer:
I do not think it is a good solution to design release stratigy through number range.Why do you use different document type for PR.for every PR document type you can assign different Release code.
Answer:
Hi Orange1,
I have tried to make the similar simulation in my system and it is working fine. What was the Data Type you have selected? Of course, if you selected 'CHAR' type, it is not possible for you to get the 'Interval value', but 'Multiple values' choice. Let make another try and get back to me.
Cheers,
HT
Answer:
I'm letting SAP default the data type to CHAR from the CEBAN-AUFNR entry in the Characteristic. Are you defining your data type manually?
If so, how does the release strategy check the characteristic against the PREQ Order @?
Thanks for the reply.........
Orange1
.
Answer:
Hi Orange1,
Actually, we are using Data type 'Numeric value' and defining the interval value as characterisitics value on which the validation of proper release strategy is based. In the case of 'CHAR' Data type, then you have to maintain all of your Order number in the Characteristics Value in CT04 transaction which is time-consuming. Again, it is very much subject to how you have define your Order numbering system to determine the appropriate data type.
Cheers,
HT
Answer:
My order # range are like this.....1100000-1199999 and 1200000 - 1299999. The field AUFNR in CEBAN is a CHAR, what field are you using within your characteristic to capture order #? Are you using the user exit?
If you are using AUFNR, I'd be interested to see how many characters long the field is, and what the # range values look like......
THanks again.
Orange1
Answer:
Hi Orange1,
If that is of your Order numbering range, then you have to change your Data type from 'CHAR' into 'Numeric format' so that you can flag on the 'Interval values allowed' checkbox.
Cheers,
HT
Answer:
It won't let me, the field is "Greyed Out".
Orange1
Answer:
Hi Orange1,
It worked fine to me ie. I can go to Transaction CT04 and change the 'Data Type'. What have you done so far?.
Cheers,
HT
Answer:
I sent you a screen shot of CT04
Answer:
anyone else have any ideas?

More Articles:

Error Log?
delete PO?
Subsequent debit/MIRO, tax problem.?
MC.9 Spool request?
Baseline configuration?
vendor?