PO Splitting Rules/ Requisition line grouping Rules for Autocreate

Hello,
I need to know what are the rules that cause requisition to split into multiple PO's when auto generated?
I know two profile values 'PO: Use Need-by Date for Default Autocreate grouping' or 'PO: Use Ship-to Organization and Location for Default Autocreate grouping' that we can setup. Are there any such profile options available? Or can we change to add or remove the requisition line grouping rules? If yes, how to achieve that?
Our business is inquiring if it is possible to suppress grouping based on Buyer? We have case where single requisition had multiple lines. This requisition generated 3 unique PO's based on buyer.
Any impits will be appreciated.
Thanks,
Anish

Hello Sandeep,
Thank you for your response.
Our buyer do not go to autocreate screen. When purchasing requisition is approved, it automatically generates PO.
Our business wants to remove requistion grouping based on BUyer. Eg: Currently if requisition has 3 lines with 3 different category items and each category has different Buyer assigned to it, then autocreate process will generate 3 unique PO's for this one requisition.
Thanks,
Anish

Similar Messages

Delete Requisition Lines, Freight Charges for po

I was wondering if anyone knows how to delete individual requisition lines after approval.
Also, We are using the Unit price in PO level as C+F. But that could affected in item average cost, So how we can handle the PO which has Friegth charges without affecting on the accuracy of Average price and while matching the Invoice with PO (In case if we put the frieght charges as another item).

HI,
Go to M/06.select the frieght condition type and tick the group condition indicator and Group condition routine as 1 Overall document .and then enter condition value at header level in PO.
reward if helpful.
Regards,
Chetan.

CREATE SUBSTITUTION RULE FOR u0093COPYING LINE ITEM TEXT FOR LINE ITEMSu0094

Hi every body
When user post transactions in FB60 we have give the line item text, Suppose no.of lineitems are there in tht instnace my client asked to create the substitution rule to COPYING LINE ITEM TEXT FOR LINE ITEMS
pls tell me the processes how to create the substitution rule
Plz can anyboby help me out...
laxmi velaga

sorry,
link doesn't work:
here's the content:
you must add your rules at event 3 (complete document)
in an exit of ZGGBS000:
data htext type bseg-sgtxt.
*find
LOOP AT BOOL_DATA-BSEG INTO BSEG
WHERE bseg-sgtxt <> space.
move bseg-sgtxt to htext.
ENDLOOP.
*copy
LOOP AT BOOL_DATA-BSEG INTO BSEG
WHERE bseg-sgtxt = space.
move htext to bseg-sgtxt
*modify
MODIFY BOOL_DATA-BSEG FROM BSEG.^
ENDLOOP.
http://help.sap.com/saphelp_47x200/helpdata/en/5b/d231a843c611d182b30000e829fbfe/frameset.htm
please reward useful answers
thanks and regards
Andreas

ISE: create rules with AD groups for Users and Computers

Hello,
We've just begun to work with ISE.
Is it the good place to post on ISE, or there is a dedicated forum in another place?
We'd like to create some rule depending of Computer member groups AND Users member groups from AD, but we meet some difficulties.
We've created AD groups for Computers and Users depending of their Department:
Users_1
Users_2
Computers_1
Computers_2
When we create some basics rules regarding one group only:
- with a group Computers_x to attribute a specific VLAN to a computer (when no Windows session is opened), it runs correctly.
- with a group Users_x to attribute a specific VLAN to an user (when Windows session is opened), it runs correctly.
But when we create a rule regarding a group from Computers and one from Users, to attribute a specific VLAN to an user on a specific computer, this rule is not applied.
Is it possible to use ISE on this way?
Thanks for help.
Regards,
Chris

Enable EAP Chaining— if you want Cisco ISE to allow authentication of both machine and user in the same EAP-FAST authentication.
http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns742/ns744/docs/howto_80_eapchaining_deployment.pdf

Settlement Status-05 (Dist. rule group specfied for partial settlement)

Hi all,
If we execute the report CJID, we see the settlement status 05(Dist. rule group specfied for partial settlement).
My query is what does settlement status 05 exactly means.
Regards,
Gagandeep Singh

HI gagandeep singh,
settlement status 05 could be your allocation structure.
or else can you explain more abt your query
vengaiah chowdary

Use of content rule vs source group for NATing

To NAT outgoing flows out of two servers, is it necessary to define a content rule and source group (or is just a source group sufficient?).
Having trouble with Option 2.
Option 1:
service svr1
ip address 192.168.10.1
no port
protocol tcp
active
Also does CSS do NAPT i.e. alter the source port number for outgoing packets from source groups?
service svr2
ip address 192.168.10.2
no port
protocol tcp
active
content outflows
protocol tcp
add service svr1
add service svr2
vip address <externalip>
active
group outgrp
vip address <external ip>
add service svr1
add service svr2
active
<add appropriate acl>
Option 2:
service svr1
ip address 192.168.10.1
no port
protocol tcp
active
service svr2
ip address 192.168.10.2
no port
protocol tcp
active
group outgrp
vip address <external ip>
add service svr1
add service svr2
active
<add appropriate acl>

to nat connections initiated by the server, you only need a source group.
No need for a content rule.
The CSS will port nat.
Gilles.

Autoinvoice Group Rules - Grouping of multiple Sales Orders

I have this requirement to group invoices by subinventory, ship-to address and PO number, all these coming from the Order Entry form. What it means is that multiple Sales Orders having the same subinventory, ship-to address and PO number and also with Receivable Interface, Interfaced, should be grouped into a single invoice. Could you please advise what are the steps needed to do this. From the list of values for the Optional Grouping Characteristics in the Autoinvoice Group Rules form, I do not see the values like subinventory, ship-to address or PO number. Do I have to associate them (subinventory, ship-to address and PO number) with some of those in the list of values (eg, Line Level Descriptive Attribute1, Line Level Global Attribute1 or Transaction Flexfield Attribute1). Is there any order or procedure to associate them and where and how do I associate them? Your detailed advice to this is much appreciated. Thank you very much. God bless you

Bill
Yes you do have to associate functional entities like suninventory with the appropriate columns in the interface table.
For a comprehensive list of columns and the data they contain, refer the Open Interfaces manual for OE - you can find a section where it describes column by column what info gets transferred to AR. I am sorry I don't remember the exact section names..i don't have access to a manual right now..later maybe!!

R11i - AR Autoinvoice - Mandatory grouping rules (N deliveries = 1 invoice)

Hi.
We have one big client who has a lot of shipment addresses (for deliveries) and when all orders are invoiced we want to get only one invoice for all different deliveries (we cant just merge all orders in to one ship_to_address site).
The usual way for changing the way of grouping with autoinvoice is using different grouping rules (but only adding not removing):
Can the Mandatory grouping rules attributes be changed? (we would like to remove the ship_to_address attribute). Any other way to create only one invoice?
Oracle® Receivables - User Guide:
Grouping rules include mandatory attributes which are always included in all grouping
rules, and optional attributes which may be included in a grouping rule. Optional
attributes may be added to the mandatory attributes to create new grouping rules
Thanks for any help.
Kind regards,
Kristjan
Edited by: user10676522 on 28.4.2010 23:44

Hi Kristjan,
No, you cannot change the mandatory grouping rules. As you know the ship_to_customer is one of the mandatory grouping columns, so if you want shipments to multiple ship_to locations to be all in one invoice, there is no other way but to remove the ship_to references from the ra_interface_lines_all table before you run autoinvoice. This obviously means that you lose the ship_to references on your invoice. To take care of that, you can pass on the ship_to information on the transaction line flexfield.
Hope this hepls.
Thanks,
Anil

AME line level rule creation ?

Hi,
Kindly let me know how to create line level rules in Approval Management Engine.
Requirement is such that I have a header and there are lines associated with it. Each line follows a different approval flow.
Once all the lines are approved the header should become approved.
Kindly let me know how this could be achieved using AME.
Thanks.

Hello,
Primarily the job of AME is to provide you with a list of approvers based the way you have configured the same.
Now, it is possible that you can check the requisition lines and check whether a line is project based or Task based
and you will also be able to pull the approver list.
But, the question is (as mentioned earlier PranitSaha), how do you break the requisition into different lines and send them for different approvals?
I mean, how do you generate different transaction_id for each of the requisition lines if the requisition is at the header level.
Though you can get the list of approvers, the requisition may be going for approval only once.
For Eg, in Payables the workflow is designed to send the invoice for approval at the line level.
So, how do you handle it if the requisition is submitted for approval at the header level. You may have to check if the Product allows you to do that.
What is possible in AME is you can review the requisition lines whether they are Project based or Task based and you can bring in all the approvers
in the approver list.
Thanks and Regards
Niru

How Do I Create a Blank Line Mail RULE ?

I've been getting a lot of Spam that always features friend's email address's and a Blank Subject line. So I would like to create a Rule that if the Subject line is Blank, send it to the Trash.
But of course it won't let me create a rule leaving one of the fields Blank, ie. empty.
My address book has been hacked it would seem because these Spam/Junk messages for a Canadian Pharmacy always have a blank subject line, are addressed from a friend and is Cc'ed to other friends! The pharmacy's address is disguised by another address, which sometimes features something of interest to me, like Architecture! Scary ...

The following rule should do the trick:
For the "If" section, select any or all (doesn't matter when using only 1 condition).
Then select:
"Subject" >> "Is equal to" >> leave the text box empty (deleting contents if any)
For the "Perform Action" section, select "Move Message" >> "Junk"

Automatic clearing - Grouping rules

Hi All,
I try to configure the automatic clearing process but unfortunatelly the grouping variants don't work:
First rule: group by DFKKOP-XBLNR and DFKKOP-ZZ_RST3
Second rule: group by DFKKOP-XBLNR
Posting 1: xblnr = A / zz_rst3 = B / 10 EUR
Posting 2: xblnr = A / zz_rst3 = B /-10 EUR
Posting 3: xblnr = A / zz_rst3 = C / 30 EUR
Posting 4: xblnr = A / zz_rst3 = D /-30 EUR
I would like to clear:
1.- Posting 1 and 2 together
2.- Posting 3 and 4 together
Is it possible to do it without programming? I have changed in customizing grouping rules (blanc, 1, 2, 3), but it doesn't work. My results changing the grouping rules are: I clear all the postings together or I only clear the posting 1 and 2.
Your response is greatly appreciated.
Cheers,
maresp

Hi,
thank you for your answer!
Grouping rule 5? I have in customizing only 4 options for the automatic clearing (blanc, 1, 2, 3, 4)
Cheers
maresp
Edited by: maresp on Oct 5, 2010 10:22 AM

AUTOINVOICE GROUPING RULE

제품: Applications
작성날짜 : 2006-05-30
AUTOINVOICE GROUPING RULE
=========================
PURPOSE
Autoinvoice를 할때는 반드시 사용하는 필수 grouping조건이 있습니다.
아래의 Grouping조건에 만족하면 동일 거래로 만들어 지게 됩니다.
Explanation
Ordering and Grouping Rule list
Mandatory Grouping Characteristics
Agreement
Batch Name
Bill To Address
Bill To Contact
Bill To Customer
Comments
Commitment Document's Id
Contract ID
Conversion Date
Conversion Rate
Conversion Rate Type
Credit Method for Accounting Rule
Credit Method for Installments
Credited Document's Id
Currency
Customer Bank Account
Document Number
Document Number Sequence Id
GL Date
Imported Billing Number
Internal Notes
Invoice Date
Invoice Level Descriptive Attribute 1
Invoice Level Descriptive Attribute 10
Invoice Level Descriptive Attribute 11
Invoice Level Descriptive Attribute 12
Invoice Level Descriptive Attribute 13
Invoice Level Descriptive Attribute 14
Invoice Level Descriptive Attribute 15
Invoice Level Descriptive Attribute 2
Invoice Level Descriptive Attribute 3
Invoice Level Descriptive Attribute 4
Invoice Level Descriptive Attribute 5
Invoice Level Descriptive Attribute 6
Invoice Level Descriptive Attribute 7
Invoice Level Descriptive Attribute 8
Invoice Level Descriptive Attribute 9
Invoice Level Descriptive Category
Invoice Level Global Attribute 1
Invoice Level Global Attribute 10
Invoice Level Global Attribute 11
Invoice Level Global Attribute 12
Invoice Level Global Attribute 13
Invoice Level Global Attribute 14
Invoice Level Global Attribute 15
Invoice Level Global Attribute 16
Invoice Level Global Attribute 17
Invoice Level Global Attribute 18
Invoice Level Global Attribute 19
Invoice Level Global Attribute 2
Invoice Level Global Attribute 20
Invoice Level Global Attribute 21
Invoice Level Global Attribute 22
Invoice Level Global Attribute 23
Invoice Level Global Attribute 24
Invoice Level Global Attribute 25
Invoice Level Global Attribute 26
Invoice Level Global Attribute 27
Invoice Level Global Attribute 28
Invoice Level Global Attribute 29
Invoice Level Global Attribute 3
Invoice Level Global Attribute 30
Invoice Level Global Attribute 4
Invoice Level Global Attribute 5
Invoice Level Global Attribute 6
Invoice Level Global Attribute 7
Invoice Level Global Attribute 8
Invoice Level Global Attribute 9
Invoice Level Global Attribute Category
Invoicing Rule
Memo Reason
Payment Set Id
Payment Terms
Primary Salesperson
Printing Option
Purchase Order
Purchase Order Date
Purchase Order Revision
Receipt Method
Related Document
Sales Territory
Set of Books Id
Ship To Address
Ship To Contact
Ship To Customer
Sold To Customer
Transaction Number
Transaction Type
Example
Reference Documents
5459900.992

제품: Applications
작성날짜 : 2006-05-30
AUTOINVOICE GROUPING RULE
=========================
PURPOSE
Autoinvoice를 할때는 반드시 사용하는 필수 grouping조건이 있습니다.
아래의 Grouping조건에 만족하면 동일 거래로 만들어 지게 됩니다.
Explanation
Ordering and Grouping Rule list
Mandatory Grouping Characteristics
Agreement
Batch Name
Bill To Address
Bill To Contact
Bill To Customer
Comments
Commitment Document's Id
Contract ID
Conversion Date
Conversion Rate
Conversion Rate Type
Credit Method for Accounting Rule
Credit Method for Installments
Credited Document's Id
Currency
Customer Bank Account
Document Number
Document Number Sequence Id
GL Date
Imported Billing Number
Internal Notes
Invoice Date
Invoice Level Descriptive Attribute 1
Invoice Level Descriptive Attribute 10
Invoice Level Descriptive Attribute 11
Invoice Level Descriptive Attribute 12
Invoice Level Descriptive Attribute 13
Invoice Level Descriptive Attribute 14
Invoice Level Descriptive Attribute 15
Invoice Level Descriptive Attribute 2
Invoice Level Descriptive Attribute 3
Invoice Level Descriptive Attribute 4
Invoice Level Descriptive Attribute 5
Invoice Level Descriptive Attribute 6
Invoice Level Descriptive Attribute 7
Invoice Level Descriptive Attribute 8
Invoice Level Descriptive Attribute 9
Invoice Level Descriptive Category
Invoice Level Global Attribute 1
Invoice Level Global Attribute 10
Invoice Level Global Attribute 11
Invoice Level Global Attribute 12
Invoice Level Global Attribute 13
Invoice Level Global Attribute 14
Invoice Level Global Attribute 15
Invoice Level Global Attribute 16
Invoice Level Global Attribute 17
Invoice Level Global Attribute 18
Invoice Level Global Attribute 19
Invoice Level Global Attribute 2
Invoice Level Global Attribute 20
Invoice Level Global Attribute 21
Invoice Level Global Attribute 22
Invoice Level Global Attribute 23
Invoice Level Global Attribute 24
Invoice Level Global Attribute 25
Invoice Level Global Attribute 26
Invoice Level Global Attribute 27
Invoice Level Global Attribute 28
Invoice Level Global Attribute 29
Invoice Level Global Attribute 3
Invoice Level Global Attribute 30
Invoice Level Global Attribute 4
Invoice Level Global Attribute 5
Invoice Level Global Attribute 6
Invoice Level Global Attribute 7
Invoice Level Global Attribute 8
Invoice Level Global Attribute 9
Invoice Level Global Attribute Category
Invoicing Rule
Memo Reason
Payment Set Id
Payment Terms
Primary Salesperson
Printing Option
Purchase Order
Purchase Order Date
Purchase Order Revision
Receipt Method
Related Document
Sales Territory
Set of Books Id
Ship To Address
Ship To Contact
Ship To Customer
Sold To Customer
Transaction Number
Transaction Type
Example
Reference Documents
5459900.992

Maximum number of rules in Numbers? Scrolling for 'show rules'?

I am trying to apply multiple conditional rules to a group of cells but can only get about 13 applied before 'show rules' runs out of space (and can't scroll down to add more). Am I missing something? Any help greatly appreciated - thanks

Thank-you for the help.
I thought I must be missing something because it seems so easy and obvious for Apple to make these rules srcollable. As Jerry says, they probably did't think to try off their 27" screens!
The only trouble with inserting extra rules is of course that it then makes it a 'faff' to later edit or remove rules that have been taken off the viewable screen.
Thanks again.
Ian

Requisition import has grouped all the requisition lines in one requisition

HI
I need a help.
Requisition import has grouped all the requisition lines (having sourcing supplier and inventory)in one requisition
for whcih the type lookup code is 'Purchase'. the source of requisition was MRP. How the system can group the items having different sourcing(few are from supplier and few are from inventory) into one requisition.
Is this the oracle standard functionality
Thanks
Payal

See req import group by parameter is playing a role here..
I think maybe it is considering ALL and clubbing together to one..not sure though
See if these threads can help the cause
Unable to avoid Autocreate PO grouping by different Supplier
Autocreate PO - default requisition grouping
Mahendra

Field status group rules in FI

Hi experts,
I have some FI data in a Excel sheet.
In that Excel sheet i have header data.Some hearder data is in one color and some header data is in another color.
So while posting this data into SAP i have to apply field status group rules( for required and suppress fields)..Can any body have any example code for this ?
Regards

Hi,
use fm FI_FIELD_SELECTION_DETERMINE
Re: Access to GL Field Status Group Settings
A.

PO Splitting Rules/ Requisition line grouping Rules for Autocreate

Similar Messages

Maybe you are looking for