Customer wise Billing type

Dear gurus
I have folllowing requirement.
We want to have separate Billing type for certain customers.
But order processing will be through stadard order type OR for all customers.
Is this possible.
BJ

hi,
The document types are independent of customers. The billing docuemnt type takes reference either from delivery or order doc type.Hence for specific customer with same order type u can't have different billing types.
You can try this, confi order type, delivery type & billing type for the specific customer else please consult with ur abaper for ur requirement
regards,
Arun prasad

Similar Messages

Updating custom field bill type in standard table ERCH

Hi All,
I need to update the custom field bill type in table ERCH depending upon the bill transaction( if bill transaction is periodic,bill type will be updated as P and so on for other cases)
I am implementing a BADI ISU_DEF_BILL_PERIOD and i have used case statements(when abrvorg is P,bill type is P). While debugging i saw that the importing parameter bill document is generated but if i enter the same bill document number at that point in time in table ERCH, it shows no entries found. Thus sy-subrc is retrieved as not zero and hence the custom field bill type does not get updated.
I would like to know how do i go about this requirement since it seems that the bill document entry is made in table ERCH outside this BADI.I used x_new_billing_doc-erch-zbill_type = 'P' in the code but it says that it cannot be changed. Any structure which can be used to be filled here?
Thanks,
Shreeraj

Sheeraj,
You're using a wrong enhancement for your requirement. ISU_DEF_BILL_PERIOD is used to specify billing key date of a billing or print document depending on your requirements,.
SAP provides enhancement EBIA0001 for any custom enhancements to billing document. You can update the custom fields in the billing document before the document is updated.
Best,
Sai

Customer wise Billed quantity and Receivables

Dear All,
Is there any standard report in which I can have Billed quantity and Receivables (collection amount ) based on the customer and date wise ,
Regards
R Dhana

Hi Dhana,
Check the below T-Codes it will be helpfull+FD10N
1.S_ALR_87012167-Accounts Rec. Information System
2.S_ALR_87012172-Customer Balances in Local Currency
3.S_ALR_87012186-Customer Sales
4.S_ALR_87012169-Transaction Figures: Account Balance
5.S_ALR_87012168-Due Date Analysis for Open Items
6.S_ALR_87012197-List of Customer Line Items
7.S_ALR_87012174-List of Customer Open Items
8.S_ALR_87012175-Open Items: Customer Due Date Forec.
9.S_ALR_87012178-Customer Open Item Analysis(Overdue)
Regards,
Venugopal

Billing Doc. Wise & Customer Wise Report

Hi Experts ,
I want to view a Report which will show following Things:
1) Cummulative Balances ( Debit / Credit ) of all my customers in a Single Screen
2) Bifurcation of Cummulative Total of Each Customer as per billing type Wise ( Supply/ Erection / Civil etc..)
We have maintained Different Typs of Billing Document for each type of Billing in SAP.
Kindly provide your helpful suggestions to guide me , else we have to develop a Z Report in order to cater this requirement.
Thanks in Advance
Regards
Honey

Hi Sachin,
Use report S_ALR_87012172 for check the debit & credit total of customers.If need you can set your own layout in this report.
for point no.2 pls follow the report suggested by Mukund, if you need any other help pls revert back.
Close the thread if your issue gets resolved with the solutions
Regards
Sanjay

How to get list of docs for particulat billing type on plant wise

very urgent
is there any t-code, report to look thi
how to get list of billing docs grnerated for particulat billing type and if possible on plant wise also
very urgetnt
points to be rewarded
eagerly waitng from sap gurus

Dear chakri
As you may be aware, in VF05 you need to enter either Payer Code or Material Code and then based on the selection criteria, the report will generate. Please give the (ensure that this code is exist in billing document) Payer code and now select "Further sel.criteria" and DONT forget to enter the date in from column of "Billing docs.date". By default, there you can see one month date range.
Still if you get error message, please let me know the error message.
thanks
G. Lakshmipathi

Report for Customer wise Payment

Hi All,
I want a report for Customer who has been maintained on Cash Basis ( One Time Customer). The customer are sold on cash so there is only one entry passed inm FI that is
Bank A/c Dr
To Sales A/C Cr
That means we donot have record customer wise in SAP. But since billing document is created for these customers too, we might be having some report.
I want if there is any report in SD or FI which can give e cutomer wise payment details
Thanks in Advance. I am quite liberal in assigning points.
Rg
VK

Hi,
You can write a custom report to pull the data , say from BSID, BSEC with documnetnumber as key field.
Hope this helps.
Thanks,
Vamsi

How to change the billing type Rv to DG

Dear all,
when ever we are doing the return order to a sales we will create a customer credit memo through the VF01 T-code.where billing type will be customize one that is credit memo..
once we save that the in customer G/L we are getting the document type as RV instead of DG.
please tell me how to change the document Type in customer Ledger.
regards,
chethan

Hi,
Just to draw your attention that DG is doc.type used to issue credit memo from FI (t.code FB75), where it does not involve the inventory movement.
Whereas the credit memo generated from OTC cycle (i.e.VF01) involves inventory movement. Ideally, both of these types of credit memos should have different doc. types, so that users can distinguish the returns based on doc. types later on.
So, after explaining the above, please check with your business thoroughly if they really need to use DG instead of RV. I would suggest to create new doc. type 'ZC' and set up through VOFA.
Thanks,
Nirav

Delivery type LR cannot be invoiced with billing type RE?

Hi,
I am refering below flow to create an return order, but face an error when creating credit billing document:
ret sale order(RE)-ret delivery(LR)-post goods receipt(stock will be restored in corresponding storage loc)---credit for return(RE)
Error msg: " Delivery type LR cannot be invoiced with billing type RE;
Check the table entries for the copying control of billing
documents and add the missing entries as necessary.
Make the appropriate settings in Customizing if you have
the authorization to do so."
So i guess i might need maintain corresponding copying control for 'delivery document to billing document'...As the source order type is LR, and target order type is RE...I checked SPRO and found there are below inputs needed. May i know what kind of data should be inputed normally??
"Copying requirements
Determ.export data
Assignment Number
Reference number"
Thank you very much!!

Hi
In standard SAP credit memo for sale returns with refrence to return order only. (RE). Thats why you are getting this error. If your requirement is to refer the delivery quantity for the credit memo then you can do any one of the following
1. Change the copy control setting for Return order to Credit memo.
    Go to VTFA transaction and select your return order type (RE) and Credit memo type (RE) and go to item category level and select your returns item category (REN) and change the billing quantity to 'D' -Delivery quantity.
    Now create your credit note with reference to your returns sale order. (not delivery). Onlly delivered quantity will be copied to the credit memo.
2. If you want to create return credit memo with reference to your return delivery then follow the first two guy's reply. Also you have to do one more setting at your return order document type (RE).
   Go to VOV8 and enter ur return order type and go to details then enter the return credit memo type in the delivery related billing field. (FKARV) in the billing section.
Regards
Shiva

Pricing procedure in billing type

How can I change pricing procedure in billing type

Hi,
Go to Tcode ovkk Transaction code and enter your sales area details(for which sales area you had created this pricing procedure) and customer pricing procedure(you can assign this in by using T.code XD02 sales area data sales tab and pricing procedure) and dcocument pricing procedure,which u had assigned in ur billing doc type(check by using T.code VOFA and go to ur billing type and check in views of account assignment and pricing -
pricing)

Datasource or Cube for GL wise customer wise sales report

Hi BI Masters,
I am using Bi. 7.0, there is requirement for Sales report i.e. 'GL wise customer wise Sales Report '. For this i am searching standard datasource or cube which can help to develop the desire report. i shall appreciate all of you if you can share your experience in this type of requirement.
With Best Regards & Thanks
Kamal Purohit
INDIA

Hi,
Check the following datasource in ECC in RSA5.
0FI_GL_10                         General Ledger: Leading Ledger Balances
0FI_GL_11                         General Ledger: Balances of Leading Ledger via Line Items
0FI_GL_12                         General Ledger: Balances of Leading Ledger via Delta Queue
0FI_GL_2                          General ledger: Transaction figures - Cost of sales ledger
0FI_GL_4                          General Ledger: Line Items with Delta Extraction
0FI_GL_6                          General Ledger Sales Figures via Delta Extraction
0FI_GL_7                          General Ledger Cost of Sales Ledger via Delta Extraction
0FI_GL_8                          General Ledger: Statistical Key Figures
0FI_TX_4                          Taxes: Line Items by Means of Delta Extraction
Thanks
Reddy

Accounts Receivable Report: Customer Wise Ageing Analysis report -FI module

Hi Gurus,
             Can anyone help me in providing standard report(source code) or already done sample report(source code) for Accounts Receivable Report: Customer Wise Ageing AnalysisThis is in FI Module. Though it is FI Module we need to fetch details related to Sales Module, and the days should be <0     30     60     90     120     180     365     >365
It is urgent I need to deliver this report by this week end.
Please help me . Waiting for your reply.
Points Rewarded for help rendered and I would personally send a good gift if you can help me
Yours Truly,
Rajiv Christopher.
Edited by: Rajiv Christopher on Apr 2, 2008 11:33 AM

Hi,
i am attaching aging report.
see if this is useful to you.
REPORT ZFUS0102 MESSAGE-ID OA
                LINE-SIZE 270.
Title:      GR/IR AGING REPORT
Date:       January 2001
TABLES: DISVARIANT, EKPO.
TYPE-POOLS: SLIS.
Tables
TABLES:
BSIS,
EKKO.
working table
DATA: BEGIN OF RTAB OCCURS 0,
         HKONT   LIKE BSIS-HKONT,
         ZUONR   LIKE BSIS-ZUONR,
         BUDAT   LIKE BSIS-BUDAT,
         SHKZG   LIKE BSIS-SHKZG,
         DMBTR   LIKE BSIS-DMBTR,
         PRCTR   LIKE BSIS-PRCTR,
      END OF RTAB.
DATA: BEGIN OF WTAB OCCURS 0,
         ZUONR(2) TYPE N,
         PRCTR   LIKE BSIS-PRCTR,
         DAYS(4) TYPE P,
         DMBTR   LIKE BSIS-DMBTR,
      END OF WTAB.
DATA: BEGIN OF PTAB OCCURS 0,
         ZUONR(2),
         PRCTR   LIKE BSIS-PRCTR,
         AMT30   LIKE BSIS-WRBTR,
         AMT60   LIKE BSIS-WRBTR,
         AMTPL   LIKE BSIS-WRBTR,
         TOTAL   LIKE BSIS-WRBTR,
      END OF PTAB.
PARAMETERS: COMPANY LIKE BSIS-BUKRS OBLIGATORY,
             ACCT    LIKE BSIS-HKONT OBLIGATORY,
             DATE    LIKE SY-DATUM OBLIGATORY.
SELECT-OPTIONS: S_EKORG FOR EKKO-EKORG.
PARAMETERS: P_VARI LIKE DISVARIANT-REPORT.
DATA: WS-AMT30 LIKE BSIS-WRBTR.
DATA: WS-AMT60 LIKE BSIS-WRBTR.
DATA: WS-AMTPL LIKE BSIS-WRBTR.
DATA: TITLE(21) VALUE 'GR/IR Aging Report'.
DATA: LIN TYPE I.
DATA: GX_VARIANT LIKE DISVARIANT,
      G_VARIANT LIKE DISVARIANT.
DATA: LAYOUT   TYPE SLIS_LAYOUT_ALV,
       L_F      TYPE SLIS_T_FIELDCAT_ALV   WITH HEADER LINE,
       GROUP    TYPE SLIS_T_SP_GROUP_ALV   WITH HEADER LINE,
       COLOR    TYPE SLIS_T_SPECIALCOL_ALV WITH HEADER LINE.
DATA: LT_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER,
       LS_LINE TYPE SLIS_LISTHEADER,
       T_EVENTS   TYPE SLIS_T_EVENT.
CONSTANTS: FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE'.
INITIALIZATION.
PERFORM EVENTTAB_AUFBAUEN USING T_EVENTS[].
PERFORM VARIANT_INIT.
Get default variant
GX_VARIANT = G_VARIANT.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
       EXPORTING
            I_SAVE     = 'A'
       CHANGING
            CS_VARIANT = GX_VARIANT
       EXCEPTIONS
            NOT_FOUND = 2.
IF SY-SUBRC = 0.
    P_VARI = GX_VARIANT-VARIANT.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
PERFORM VARIANT_INPUTHELP_F14.
START-OF-SELECTION.
LS_LINE-TYP = 'S'.
WRITE SY-DATUM TO LS_LINE-INFO DD/MM/YY.
WRITE SY-UZEIT TO LS_LINE-INFO+10.
WRITE SY-UNAME TO LS_LINE-INFO+20.
WRITE TITLE    TO LS_LINE-INFO+30.
APPEND LS_LINE TO LT_TOP_OF_PAGE.
PERFORM FIELDS.
IF NOT P_VARI IS INITIAL.
    PERFORM PAI_OF_SELECTION_SCREEN.
ELSE.
    CALL FUNCTION 'REUSE_ALV_VARIANT_SELECT'
         EXPORTING
              I_DIALOG            = ' '
              I_USER_SPECIFIC     = 'A'
              I_DEFAULT           = ' '
        I_TABNAME_HEADER    =
        I_TABNAME_ITEM      =
              IT_DEFAULT_FIELDCAT = L_F[]
              I_LAYOUT            = LAYOUT
         IMPORTING
        E_EXIT              =
              ET_FIELDCAT         = L_F[]
        ET_SORT             =
        ET_FILTER           =
         CHANGING
              CS_VARIANT          = DISVARIANT
         EXCEPTIONS
              WRONG_INPUT         = 1
              FC_NOT_COMPLETE     = 2
              NOT_FOUND           = 3
              PROGRAM_ERROR       = 4
              OTHERS              = 5.
ENDIF.
Decide which tables to access.
PERFORM MAIN_SELECT.
MOVE TITLE TO LAYOUT-WINDOW_TITLEBAR.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
       EXPORTING
            I_CALLBACK_PROGRAM      = 'ZFUS0102'
            I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
            IS_LAYOUT               = LAYOUT
            IT_FIELDCAT             = L_F[]
            IT_SPECIAL_GROUPS       = GROUP[]
            I_SAVE                  = 'A'
            IS_VARIANT              = G_VARIANT
            IT_EVENTS               = T_EVENTS
       TABLES
            T_OUTTAB                = PTAB
       EXCEPTIONS
            PROGRAM_ERROR           = 1
            OTHERS                  = 2.
      FORM FIELDS                                                   *
FORM FIELDS.
L_F-FIELDNAME     = 'ZUONR'.
L_F-OUTPUTLEN     = 6.
L_F-SELTEXT_L     = 'SERIES'.
L_F-REPTEXT_DDIC = 'SERIES'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'PRCTR'.
L_F-OUTPUTLEN     = 10.
L_F-SELTEXT_L     = 'PROFIT CTR.'.
L_F-REPTEXT_DDIC = 'PROFIT CTR.'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'AMT30'.
L_F-SELTEXT_L     = '30 DAYS'.
L_F-REPTEXT_DDIC = '30 DAYS'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'AMT60'.
L_F-SELTEXT_L     = '60 DAYS'.
L_F-REPTEXT_DDIC = '60 DAYS'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'AMTPL'.
L_F-SELTEXT_L     = '60+ DAYS'.
L_F-REPTEXT_DDIC = '60+ DAYS'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'TOTAL'.
L_F-SELTEXT_L     = 'TOTAL'.
L_F-REPTEXT_DDIC = 'TOTAL'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
ENDFORM.
      FORM MAIN_SELECT                                              *
FORM MAIN_SELECT.
SELECT HKONT ZUONR BUDAT SHKZG DMBTR PRCTR
       INTO TABLE RTAB
       FROM BSIS
       WHERE BUKRS = COMPANY
       AND   HKONT = ACCT.
IF SY-SUBRC = 0.
    SORT RTAB.
    PERFORM PROCESS_RTAB.
    PERFORM PROCESS_WTAB.
ENDIF.
ENDFORM.                    " MAIN SELECT
      FORM VARIANT_INPUTHELP_F14                                    *
FORM VARIANT_INPUTHELP_F14.
DATA: G_EXIT(1) TYPE C.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
       EXPORTING
            IS_VARIANT          = G_VARIANT
            I_SAVE              = 'A' " g_save
          it_default_fieldcat =
       IMPORTING
            E_EXIT              = G_EXIT
            ES_VARIANT          = GX_VARIANT
       EXCEPTIONS
            NOT_FOUND = 2.
IF SY-SUBRC = 2.
    MESSAGE ID SY-MSGID TYPE 'S'      NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
    IF G_EXIT = SPACE.
      P_VARI = GX_VARIANT-VARIANT.
    ENDIF.
ENDIF.
ENDFORM.
      FORM USER_COMMAND                                             *
--> UCOMM                                                         *
--> SELFIELD                                                      *
FORM USER_COMMAND USING UCOMM LIKE SY-UCOMM SELFIELD TYPE
SLIS_SELFIELD.
IF UCOMM EQ '&IC1'.
    IF SELFIELD-TABINDEX <= 0.
      MESSAGE S108.
      EXIT.
    ENDIF.
IF SELFIELD-SEL_TAB_FIELD CS 'LIFNR'.
    SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
    CALL TRANSACTION 'XK02'.
ELSE.
    IF SELFIELD-SEL_TAB_FIELD CS 'VEND'.
      SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
      CALL TRANSACTION 'FBL1'.
    ENDIF.
ENDIF.
    CLEAR SY-UCOMM. CLEAR UCOMM.
ENDIF.
ENDFORM.
      FORM TOP_OF_PAGE                                              *
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
       EXPORTING
            IT_LIST_COMMENTARY = LT_TOP_OF_PAGE.
ENDFORM.
      FORM EVENTTAB_AUFBAUEN                                        *
--> P_T_EVENTS                                                    *
FORM EVENTTAB_AUFBAUEN USING P_T_EVENTS TYPE SLIS_T_EVENT.
DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
       EXPORTING
            I_LIST_TYPE = 0
       IMPORTING
            ET_EVENTS   = P_T_EVENTS.
READ TABLE P_T_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                                                 INTO LS_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_TOP_OF_PAGE TO LS_EVENT-FORM.
    APPEND LS_EVENT TO P_T_EVENTS.
ENDIF.
ENDFORM.                               " EVENTTAB_AUFBAUEN
      FORM PAI_OF_SELECTION_SCREEN                                  *
FORM PAI_OF_SELECTION_SCREEN.
IF NOT P_VARI IS INITIAL.
    MOVE G_VARIANT TO GX_VARIANT.
    MOVE P_VARI TO GX_VARIANT-VARIANT.
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
         EXPORTING
              I_SAVE     = 'A' " g_save
         CHANGING
              CS_VARIANT = GX_VARIANT.
    G_VARIANT = GX_VARIANT.
ELSE.
    PERFORM VARIANT_INIT.
ENDIF.
ENDFORM.                               " PAI_OF_SELECTION_SCREEN
      FORM VARIANT_INIT                                             *
FORM VARIANT_INIT.
CLEAR G_VARIANT.
G_VARIANT-REPORT = 'ZFUS0102'.
ENDFORM.                               " VARIANT_INIT
*&      Form PROCESS_RTAB
      text
--> p1        text
<-- p2        text
FORM PROCESS_RTAB.
DATA TLNS TYPE I.
DESCRIBE TABLE S_EKORG LINES TLNS.
LOOP AT RTAB.
    IF TLNS GT 0.
      SELECT SINGLE EKORG FROM EKKO INTO EKKO-EKORG
        WHERE EBELN = RTAB-ZUONR(10).
      CHECK EKKO-EKORG IN S_EKORG.
    ENDIF.
    IF NOT RTAB-BUDAT > DATE.
      MOVE RTAB-ZUONR(2) TO WTAB-ZUONR.
      COMPUTE WTAB-DAYS = DATE - RTAB-BUDAT.
      IF RTAB-SHKZG = 'H'.
        WTAB-DMBTR = RTAB-DMBTR * -1.
      ELSE.
        WTAB-DMBTR = RTAB-DMBTR * 1.
      ENDIF.
      MOVE RTAB-PRCTR TO WTAB-PRCTR.
      APPEND WTAB.
    ENDIF.
ENDLOOP.
FREE RTAB.
ENDFORM.                    " PROCESS_RTAB
*&      Form PROCESS_WTAB
      text
--> p1        text
<-- p2        text
FORM PROCESS_WTAB.
SORT WTAB BY ZUONR PRCTR DAYS.
LOOP AT WTAB.
    PTAB-ZUONR = WTAB-ZUONR.
    PTAB-PRCTR = WTAB-PRCTR.
    AT END OF DAYS.
      SUM.
      IF WTAB-DAYS > 60.
        WS-AMTPL = WS-AMTPL + WTAB-DMBTR.
      ELSE.
        IF WTAB-DAYS > 30.
          WS-AMT60 = WS-AMT60 + WTAB-DMBTR.
        ELSE.
          WS-AMT30 = WS-AMT30 + WTAB-DMBTR.
        ENDIF.
      ENDIF.
    ENDAT.
    AT END OF PRCTR.
      PTAB-AMTPL = WS-AMTPL.
      PTAB-AMT30 = WS-AMT30.
      PTAB-AMT60 = WS-AMT60.
      COMPUTE PTAB-TOTAL = PTAB-AMTPL + PTAB-AMT30 + PTAB-AMT60.
      APPEND PTAB.
      WS-AMTPL = 0.
      WS-AMT30 = 0.
      WS-AMT60 = 0.
    ENDAT.
ENDLOOP.
SORT PTAB BY ZUONR PRCTR.
ENDFORM.                    " PROCESS_WTAB
regards,
Sindhu

Employee and customer wise cost

Hello Experts
Below are my business scenario
1.I want capture the employee wise cost so What could be best way to capture the employee wise expense in the below method
    Employee as cost center
    Employee as Vendor
    Employee as internal order
   IF anybody provide me advantages and disadvantage it will be better understanding
2. Another one of my requirement in my business scenario customer group wise COPA report with net profit level
Here GP level I will get it from my billing document(Revenue – COGS), customer wise expenses I am going to capture through the cost center
finally I want to settle this cost to customer group (COPA)
Is it Possible ?
Thanks & Regards
Sri.

Hi VS
1. For employee wise expenses, you can refer the document I contributed below
http://scn.sap.com/docs/DOC-50141
The document explains how you can use Statistical IOs for this.. You can also name your Statistical Internal Orders as per the Employee Number, but I used a slightly different approach to be more scaleable
2. For customer wise expenses, while you book the expenses in F-02 or FB60, you need to click on the "Prof Segment" and enter the Customer / Product details in it
That ways you can capture the expenses at Customer level in COPA
Br. Ajay M

Assign GL ACCOunt to billing type

Dear gurus
How to change the gl account of any customized billing type.
i'm having a problem that the billing type ZF26 is assigned to a wrong gl account. i want to change that
please guide me
regards
Saad.Nisar

Hi friend,
GL account assignment is done in VKOA transaction.
But it is not according to the Billing document type.
it is as per the Sales org+ Accounting key.
In the standard the tables generally we use are 4 and 5
4 is teh combination of APPLICATIONCONDITION TYPECHART OF ACCOUNTS+ACCOUNTING KEYS
5. is the combination of APPLICATIONCONDITION TYPECHART OF ACCOUNTSSALES ORGACCOUNTING KEYS.
Based on the requirement you have to assign the GL account .
Gothrough the below link for more clarity.
http://www.sapstudymaterials.com/2007/12/sap-mm-automatic-account-determination_16.html
Search them and let s know if you need any further clarification
santosh
Edited by: santosh kumar vemuri on Jun 8, 2009 2:53 PM

Intercompany stk transport order process - Billing type determination

Dear All,
We are currently dealing one Roll-Out project for one multinational company. In that from sales side, one of the main processes defined is u201CStock Transport Purchase Order processu201D. As a regular process, outbound delivery document also created with ref to STPO.
As per the client requirement the u201CPackaging materialu201D needs to be added as additional line item in the delivery to calculate the packaging cost. We have customized that also and now u201CPackaging materialu201D is adding as a new line item in the delivery document as a non valuated material.
But the issue is, the Billing type u201CZICu201D is not getting determined while creation of billing if u201CPackaging materialu201D is added as a new line item. If u201CPackaging materialu201D is not added as a line item then, billing type is getting determined automatically without any issue.
We have checked in LIKP table, its containing the billing type as u201CZICu2019. But if packaging material is added then, the billing type determination is not happening.
We are assuming that some customizing needs to be done from MM/SD point of view. I am seeking the experts help regarding this issue to solve the problem.
Regards,
MANI

Hi
Does your goods and packing material use the same item category ? If not, is the item category for the packing material relevant for billing (TVAP-FKREL) ?
/Torben

Customer wise inspection during Delivery

Hi All,
I am having a Finished Material which will be supplied to 2 customers, say A and B. Customer A requires inspection before delivery and when the same Finished material is delivered to customer B, B does not want inspection to happen.
In material master for this material I already activated 10 inspection type.
How can I control lot creation/inspection by customer wise for same Material.
Thanks and Regards,
VV

you need to create a "Quality info record in SD". you'll find it under QM>Quality planning>Logistics Master Data-->Quality Info Record:SD.
Transactions QV51,QV52, QV53.
These are set up by material and customer.
Select "By customer" if the you don't want the inspeciton lot type 10 created. This setting tells the system that the customer will handle all inspection and no inspection at delivery should be done.
"After delivery" allows the PGI prior to UD.
"Before delivery" requires the UD to be completed prior to PGI.
Craig

Customer wise Billing type

Similar Messages

Maybe you are looking for