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

Similar Messages

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

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!!

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

EDI: Syntax error in IDoc (mandatory group/segment missing)

hi EDI/IDoc experts,
Need you help urgently. According to the requirement, i need populate a segement E1IDT01 of basic type PEXR2002 . I added the code , then run and generate an idoc , the new segment
E1IDT01 was populated, but Syntax error 26 happend. Error message as below.   It also strange that i can see E1IDKU5 populate out as usual, but some others segment disappeared , i am sure that in my code ,i didn't changed any variable related to other segement . how can i fix this problem?
EDI: Syntax error in IDoc (mandatory group missing)
Message no. E0079
Diagnosis
The segment group E1IDKU5 has the attribute 'Mandatory' in the syntax description of the basic type PEXR2002 (customer enhancement ). However, the segment group is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment group is missing.
Procedure
Please check the IDoc or the syntax description of the basic type PEXR2002 (customer enhancement ).

Hi all,
Thanks so much for your concern!
Finally ,this problem has been figured out .
Requirement is user want to use segment E1IDT01 in idoc to populate the long text they maintained in accounting document vendor item line (use FB01 to create accounting doc).
Why I made out " EDI: Syntax error in IDoc (mandatory group/segment missing)" this message out ,because I didn't fill data correctly. I missed to keep SY-TABIX in momory .
when we use Function module ,or do..enddo...or read table it_table. we should be careful that SY-TABIX is changed .So we can't just use MODIFY EDIDD_TABLE INDEX SY-TABIX in the last . we should define a local variable to keep SY-TABIX in memory and then use it to modify EDIDD_TABLE.
Follow is the final code.
IF SEGMENT_NAME = 'E1IDT01'.
TABLES :STXL.
* Define for long text getting
DATA: LIT_TLINE LIKE TLINE   OCCURS 0 WITH HEADER LINE.
DATA: LV_STRING(2000) TYPE C.
DATA: LV_TDNAME TYPE THEAD-TDNAME,
        LV_ID     TYPE THEAD-TDID     VALUE '0001',
        LV_LANG   TYPE THEAD-TDSPRAS VALUE 'E' ,
        LV_OBJ    TYPE THEAD-TDOBJECT VALUE 'DOC_ITEM'.
data:   LV_LINE   TYPE I,                " long Text lines
        LV_LEN    TYPE I,                " long Text length
        LV_TABIX LIKE SY-TABIX.
* Clear memory
CLEAR:LV_TDNAME,
        LV_STRING,
        LV_LINE,
        LIT_TLINE, LIT_TLINE[],
        LV_LEN,
        LV_TABIX.
* Keep sy-tabix memory using a variable--This is the key point
LV_TABIX = SY-TABIX.
* Combine TDNAME with company code + accounting doc + fiscal year + item number.
    CONCATENATE REGUP_DATA-BUKRS REGUP_DATA-BELNR
                 REGUP_DATA-GJAHR REGUP_DATA-BUZEI INTO LV_TDNAME.
* When vendor item has long text , read long text into lv_string
    SELECT SINGLE *
      FROM STXL
      WHERE TDOBJECT = LV_OBJ
        AND TDNAME   = LV_TDNAME
        AND TDID     = LV_ID
        AND TDSPRAS = 'E'.
    IF SY-SUBRC = 0.
      CALL FUNCTION 'READ_TEXT'
        EXPORTING
          CLIENT   = SY-MANDT
          ID       = LV_ID
          LANGUAGE = LV_LANG
          NAME     = LV_TDNAME
          OBJECT   = LV_OBJ
        TABLES
          LINES    = LIT_TLINE.
      IF NOT LIT_TLINE[] IS INITIAL.
        DESCRIBE TABLE LIT_TLINE LINES LV_LINE.
        DO LV_LINE TIMES.
          READ TABLE LIT_TLINE INDEX SY-INDEX.
          CONCATENATE LV_STRING LIT_TLINE-TDLINE INTO LV_STRING.
        ENDDO.
        LV_LEN = STRLEN( LV_STRING ).
* Make sure we only need less than 840 charicters
        IF LV_LEN > 840.
          LV_STRING = LV_STRING+0(840).
          LV_LEN    = 840.
        ENDIF.
* Populate Vendor item long text with segment E1IDT01 start from
* Fields TXT03 to TXT14.
         EDIDD_TABLE-SDATA+147(LV_LEN) = LV_STRING.
        MODIFY EDIDD_TABLE INDEX LV_TABIX.
      ENDIF.
    ENDIF.
ENDIF.

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

Programmatically disable "mandatory business rule"

Hello,
Using jdevelopper 11.1.2.3.0 and HR schema, there is my use case :
An entity object (Departments) with an attribute (DepartmentId) checked as "Mandatory". A java entity object class (DepartmentsImpl.java). In this java class, create() and doDML() methods overriden :
    protected void create(AttributeList attributeList) {
        super.create(attributeList);
        AttributeDefImpl attr = this.getEntityDef().getAttributeDefImpl("DepartmentId");
        attr.setMandatory(false);
    protected void doDML(int i, TransactionEvent transactionEvent) {
        AttributeDefImpl attr = this.getEntityDef().getAttributeDefImpl("DepartmentId");
        this.setAttribute(attr.getName(), 66);
        super.doDML(i, transactionEvent);
        attr.setMandatory(true);
    }What I want is to programmaticaly disable the "mandatory business rule" for DepartmentId attribute, because this attribute's value is programmatically set just before calling doDML().
Problem : "attr.setMandatory(false);" seems to do nothing. In validation time, the mandatory business rule is working.
What AttributeDefImpl.setMandatory() method should do? Or, what should be the right way to programmatically disable a "mandatory business rule"?
Thanks.

Nirav, reading your post, I realized that "mandatory" propertie is part of attribute definition. So I have try calling setMandatory() method in EntityDefImpl. I found a method loadAttribute() that I have overriden :
    protected void loadAttribute(DefElement defElement) {
        super.loadAttribute(defElement);
        AttributeDefImpl attr = this.getAttributeDefImpl("DepartmentId");
        if(attr!=null){
            System.out.println("DepartmentId found! after super");
            attr.setMandatory(false);
    }Changing the mandatory propertie here works fine. But, it is not suitable solution for me, because the entity definition is done just once : first time a user implement the entity object.
You suggest me to do this when AM is initialized : I haven't try yet, but I think I will have same problem, because when the entity definition is done once, it will never been redo later. (That is what I understand during my tests. Maybe I'm wrong?)
Timo, I can't simply remove the mandatory flag from the attribute, because in our application, user must be abble to choose if an entity pk is auto generated or not. (and that implies that pk attribute, checked as mandatory, could be programmatically changed to false).
There is something I don't understand : calling setMandatory() in EntityImpl.create() method has no effect. But, in same maner, if I call setUpdateableFlag(), thiw will have effect. Both method are changing Entity Attribute Definition. So why setMandatory() will have effect only during the first definition of Entity, and setUpdateableFlag() will work all the time?
Thanks for your help.

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.

Difference between Source & DESTINATION GROUP RULE in Cisco CSS

Hello All,
I am newbie for CSS. I know how flow works for normal CSS request without group rule. But whenever it comes to group rule I am pretty much
confuse about following:
- When we use source group rule & when we use destination group rule ?
- What is difference between them ?
- How the flow of data works in both of them?
Any help or explanation would be appreciated.
Thanks in advance,
Me too

the group rule determines in which direction you will do nat . consider
group USHA
vip address 10.86.178.244
add service Ushatest
active
add service says that if the server we defined with service Ushatest initiates a connection outbound through the CSS we will source nat the server address to 10.86.178.244
now consider
group DOT005
add destination service dot008
add destination service dot014
vip address 10.86.178.5
we are saying that when a client hits a content rule to get loadbalanced to one of the services we will nat the client address to 10.86.178.5
in both cases nat is overloaded (pat) so many connections can be natted to the same address.
In the case where you have a content rule that loadbalances to a server and that server does not use the CSS as its default gateway w would use add destination service to get the return traffic back to the CSS.
In the case where a server is initiating the connection and we want to hide the server address we would use add service.

What infotypes are proccessed if grouping rule XALL is used?

Hello experts,
We are implementing cuncurrent employment at one of our clients, We want to use Personnel assignment grouping rule XALL which defines that all personnel assignments of a concurrently employed person are always processed together.
However we donot want all the infotypes to be proccessed together and are not sure which are the infotypes get processed together if we use XALL.
Please let me know the list of infotypes that get processed together if we use XALL.
Appreciate your help,
Revanth.

Hello experts,
We are implementing cuncurrent employment at one of our clients, We want to use Personnel assignment grouping rule XALL which defines that all personnel assignments of a concurrently employed person are always processed together.
However we donot want all the infotypes to be proccessed together and are not sure which are the infotypes get processed together if we use XALL.
Please let me know the list of infotypes that get processed together if we use XALL.
Appreciate your help,
Revanth.

How to put Sales employee (Splcode) Mandatory Field, when adding A/R invoice

Hi,
Kindly solve, How to put Sales employee (Splcode) Mandatory Field, when adding A/R invoice.
Regards,
Rajeev.

Follow this step..
1. In SQL Server, go to the SAP B1 Database you're using.
2. then on the Object Explorer , go to Database Folder, explode the SAP DB->Programmability->Stored Procedures->SBO_SP_TransactionNotification * the only Stored Procedure that is allowed to be edited. Just right click and modify
3. Try to paste this -> and click F5
If
@object_type ='13' and @transaction_type in ('A','U')
Begin
If EXISTS
select DocEntry from ONIV
Where DocEntry = @list_of_cols_val_tab_del
and SlpCode<>'-1'
Begin
set @error_message = 'Please select the Sales Employee'
set @error = 1
END
END
Regards
Kennedy

Inconsistent updation of sales group in Sales order and invoice

Dear all,
The sales office and sales group is properly updated in the specific sales area master data of the customer but not flowing in the sales order and subsquently in the invoice. For some documents it gets updated and for others the filed is blank.
I have checked the master data and also the documents and found no errors. Please help in how to solve the issue. I need 100% updation of sales office and sales group in the order and invoice. Please advice how to solve the issue.
Regards,
Parthasarathy.R

Dear Parthasarathy,
Request You to post the same query in SD Forum
You will get quick response there
this is PP forum
Hope You Understand
Regards
kumar

Posting unplanned deliveries in invoice

This is Naresh, new to SAP MM, I read that we can post unplanned deliveries in invoice in extras tab. But I cant find where the tab was. Please can anyone tell me where to post unplanned deliveries.

Hi,
Check the activation:
Spro->MM->LIV->incoming incoving->Activate Direct Posting to G/L Accounts and Material Account
Postings...
Spro->MM->LIV->incoming incoving->Configure How Unplanned Delivery Costs Are Posted.
. check the options you want.
SAM

Deliveries not invoiced (GR-based IV) reporting solution

Hello
i have been looking for a while in SAP for a report that shows me the Goods receipts not invoiced.
We are using goods receipt based invoice verification
I know about the function of MB5S but this report is not showing me in the overview the actual deliveries not invoiced.
As we are using scheduling agreements and we have hundreds of GR per one purchsing document.
When I doubleclick in MB5S on the PO/Schedule i get info about the GR / IR but i can not really subtotal since the
Invoices do not have a negative impact.
Also i think ME2N, ME2L, ME2L are not showinng me the single deliveries not invoiced
I just can not belive that the only reliable source is table EKBE where a programm/little more complex query has to be written to access and subtotal
Did anybody have the same problem and came to a conclusion?
SAP must have tons of requests for this but I can not find any solution in OSS.
Thanks so much for your comments
Cheers
Tim

Hello Jürgen,
thanks for the awnser F4 is helping for entering the invoice for one single vendor when you have some info
about the delivery note.
With some filters back and fourth i can see only the open qty.
But on monthend you want to display over all vendors the open deliveries as with MB5S, which F4 on MIRO (RM08RL80) can not provide me.
Thanks again Juergen
Tim

Prime Infrastructure 2.0 Importing user-defined group rules

Dears,
I'm looking for a way to import rules to put devices in a user defined group.
I can see how I can create groups and rules manually, but not how I could export or import those rules.
Is this possible, or on the roadmap?
Cheers,
Michel

In the Cisco Prime Infrastructure 2.0 Deployment Guide under LMS 4.2 Data Migration there is a way to import settings from a "special" backup made from LMS.
This should allow for importing userdefined groups.
Does anyone have tried this yet?
Cheers,
Michel

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

Similar Messages

Maybe you are looking for