Company and company code

Hi friends
Can any one tell me the usefullness and functionalities of a company and company code.
Regards
Balu

hi,
company & company code:
The smallest organizational unit for which individual financial statements can be drawn up according to the relevant commercial law.
A company can consist of one or more company codes.
All company codes within a company must use the same transaction chart of accounts and the same fiscal year
breakdown. The company code currencies can be different.
A company has one local currency in which its transaction figures are recorded.
company code is highest level of organisation unit in FICO
regards,
Arun prasad
Message was edited by:
arun prasad

Similar Messages

Offset customer and vendor open items from different company codes

Dear all,
I would appreciate if you could help me with below issue:
We have 2 company codes, these 2 company codes are under one company, i.e one group.
When one company code (company code A) make vendor payment, the other company code (company code B) where this vendor is a customer and having Dr. balance, request company code A to deduct the amount receivable from B's customer, i.e vendor of company code A.
Could it be possible to do this ín SAP?
How to offset these two balances while running automatic payment F110?
I would obliged any of your advise.
Thank you very much.
Rgds,
Linh

Hi,
Please check following links
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90f33e12-aeac-2a10-2186-ed8301f778ba?overridelayout=t…
Cross company-code invoice posting and configuration - ERP Financials - SCN Wiki
Regards,
Tejas

Retreive company code data from t001k and plants from t001w based on bwkey

here is my sample code pls.
pls look into the perform PERFORM F_GET_COMPANY_CODE.
and also the link between the tables (custom) like ysda_exp_prtlog,
 Purpose: The Monthly export declaration summarizes all SAD *
 export documents produced by the system. For each *
 plant in France this declaration has to be handed to *
 the Customs Authorities, together with copies of all *
 invoices mentioned in the report. *
 Preds/Successors : - *
 External Datasets: - *
 INCLUDE PROGRAM : YYSDFORM *
 MODIFICATION LOG
Date | Change Number | Initials | Description
*01/10/03| G9DK943416 | AXJIRAP | INITIAL PROGRAM *
*03/10/03| G9DK943416 | TXHONGP | CREATE PRINT-PROGRAM FOR ACCELIO *
*26/10/03| G9DK943416 | KXSAWAS | Merge all Accelio forms into one *
*02/02/04| G9DK959869 | KXSAWAS | Bug fix for Intercompany invoice *
 | | | and updating printing no. in *
 | | | YSDA_DOC_NUMBER.
*09/02/04| G9DK960368 | KXSAWAS | TICKET AM6219029 various fix *
 | G9DK960972 | KXUMNAUY | -Add yuei for download file *
 | G9DK961073 | | -Calculate invoice in case *
 | G9DK961190 | | invoce is not yet made *
 | G9DK961211 | | -Fixed message type when there is*
 | | | no data found *
*18/02/04| G9DK961418 | PXSOPHO | -Shift the position in download *
 | | | file
*26/02/04| G9DK962077 | kxumnauy | TICKET AM6219029 various fix *
 | G9DK962238 | | TICKET AM6289971 fix export file *
 | G9DK962271 | |
*18/03/04| G9DK963806 | PXSOPHO | TICKET AM6442955,AM6384438
 | G9DK964432 | | - print only 4 chars of the
 | G9DK964590 | | export procedure *
 | | KXUMNAUY | - Fix internal report
 | | KXSAWAS | - Fix invoice currency to EUR.
 | | | - Fix SUASUNIC probelm when
 | | | download file
*09/06/04| G9DK968994 | KXUMNAUY |TICKET AM6789203
 | G9DK969188 | |- Fix box 4 to print the department
 | G9DK969246 | |code(first 2 char of the postal)
 | G9DK969319 | |- Fix to print all invoice numbers
 | G9DK969345 | |reported in the section 3
 | G9DK969466 | |- Fix in case invoice currency is
 | | |not EUR, use local currency from
 | | |accounting document
 | | |- Fix in case there are different
 | | |codes are loaded on one truck
 | | |- Fix the invoice amount in column
 | | |27 has to be the amount relating to
 | | |the line item
 | | |- Fix the issue that Pro forma
 | | |invoice for STO (ZF8)shouldn't be
 | | |counted to be the final Interco
 | | |invoice
*20/08/04| G9DK972875 | KXUMNAUY |AM7387219
 | G9DK973032 | |-Exclude samples from the internal
 | | |sections 1 and 2
 | | |-Data pages: Column 11. When the
 | | |invoice amount is less then 1.000
 | | |EUR and the quantity is less then.
 | | |1.000 then "******" (6 x *) has to
 | | |be printed
*07/02/05| G9DK983160 | RXBOONG |AM8522207
 | G9DK983168 | |Fix download to unix file
*17/08/06| G9DK9A02DZ | NKONGNG |AM1983727:
 | G9DK9A02IK | |-do not show sample orders
 | | | (order type FD or ZFD)
 | | |AM2985407:
 | | |-skip all T2L* documents
*15/12/06| G9DK9A05GB | ZZPWANA | AM10208238
 | | The Monthly Export Declaration for plant FR95
 | | is showing invoice amounts in SGD in column
 | | 27, where amounts in EUR should be shown. As
 | | the amounts are labeled as EUR in column 26
 | | this is unacceptable.The second issue is that
 | | there are no invoice numbers shown in column
 | | REM.
 | | >> ZZPWANA:AM10208238:G9DK9A05GB <<
 | | >> ZZPWANA:AM10208238:G9DK9A05GJ <<
*05/02/07| G9BK900812 | PPATTAN |AM10687113
 | G9DK9A0661 | |Correction to the Monthly Export
 | | |Declaration alpha character to
 | | |numeric field
 | |
*09/07/07| G9DK9A09ND |VSRKODA Replace plant with companycode,add
 new column plant ,add new logic to
 verify that we had received * *
 BAEcOMPLETE RESPONSE (fROM FC)
 for all the export transactions
REPORT YSDF5092 LINE-SIZE 310
 LINE-COUNT 65
 NO STANDARD PAGE HEADING
 MESSAGE-ID YSD_GENERAL.
 INCLUDE PROGRAM FOR ACCELIO *
INCLUDE YYSDFORM. "Include for Accelio Print Process
INCLUDE YSDF006B_INCLUDE.
 T A B L E S *
TABLES: NAST.
 T Y P E S *
TYPES : BEGIN OF TY_RAW,
 WERKS LIKE YSDA_EXP_PRTLOG-YY_PLANT,
*-->Begin of G9DK9A09ND -VSRKODA -09/07/2007
 BWKEY LIKE YSDA_EXP_PRTLOG-YY_PLANT,
 VALUE_FROM LIKE YCACEDI-VALUE_FROM,
*<-- End of G9DK9A09ND
 HEADER_SHT LIKE YSDA_EXP_PRTLOG-YY_HEADER_TYP,
 INTERNAL_NO LIKE YSDA_EXP_PRTLOG-YY_INTERNAL_NO, "G9DK962238
 PRINT_DATE LIKE YSDA_EXP_PRTLOG-YY_PRINT_DATE,
 PRINT_TIME LIKE YSDA_EXP_PRTLOG-YY_PRINT_TIME,
 DOCUMENT_CODE LIKE YSDA_EXP_PRTLOG-YY_DOCUMENT_CODE,
 HEADER_TYP LIKE YSDA_EXP_PRTLOG-YY_HEADER_TYP,
 DELIVERY LIKE YSDA_EXP_PRTLOG-YY_DELIVERY,
 INVOICE_AMT LIKE YSDA_EXP_PRTLOG-YY_INVOICE_AMT,
 EX_RATE LIKE YSDA_EXP_PRTLOG-YY_EX_RATE,
 CURRENCY LIKE YSDA_EXP_PRTLOG-YY_CURRENCY,
 INTERNAL_NO LIKE YSDA_EXP_PRTLOG-YY_INTERNAL_NO, "G9DK962238
 EXTERNAL_NO LIKE YSDA_EXP_PRTLOG-YY_EXTERNAL_NO,
 COMMODITY LIKE YSDA_EXP_PRTLOG-YY_COMMODITY,
 REPORT_FLAG LIKE YSDA_EXP_PRTLOG-YY_REPORT_FLAG, "G9DK962077
 END OF TY_RAW.
TYPES : BEGIN OF TY_DATA,
 HEADER_TYP LIKE YSDA_EXP_PRTLOG-YY_HEADER_TYP,
 INTERNAL_NO LIKE YSDA_EXP_PRTLOG-YY_INTERNAL_NO,
 PRINT_DATE LIKE YSDA_EXP_PRTLOG-YY_PRINT_DATE,
 ZOLLA LIKE EIKP-ZOLLA,
 STGBE LIKE EIKP-STGBE,
 EXPVZ LIKE EIKP-EXPVZ,
 CONTA LIKE EIKP-CONTA,
 IEVER LIKE EIKP-IEVER,
 PDEST LIKE KNA1-LAND1,
 1DEST LIKE KNA1-LAND1,
 COMMODITY LIKE YSDA_EXP_PRTLOG-YY_COMMODITY,
 STATISTIC TYPE I,
 LFIMG LIKE LIPS-LFIMG,
 L15 TYPE I,
 REGFI(2),
 CURRENCY LIKE YSDA_EXP_PRTLOG-YY_CURRENCY,
 INVOICE_AMT TYPE I,
 ZDELN LIKE VBRK-VBELN,
 LIVRE(4),
 EXPRF LIKE EIPO-EXPRF,
 EXART LIKE EIPO-EXART,
 NTGEW LIKE LIKP-NTGEW,
 YY_SEQTAXNO LIKE VBRK-YY_SEQTAXNO, "G9DK959869
 END OF TY_DATA.
TYPES : BEGIN OF TY_HEADER,
 HEADER_SHT LIKE YSDA_EXP_PRTLOG-YY_HEADER_TYP,
 HEADER_TYP LIKE YSDA_EXP_PRTLOG-YY_HEADER_TYP,
 PRINT_NO LIKE YSDA_DOC_NUMBER-YY_PRINT_NO,
 WERKS LIKE T001W-WERKS,
*-->Begin of G9DK9A09ND -VSRKODA -09/07/2007
 BUKRS LIKE T001K-BUKRS,
 BWKEY LIKE T001K-BWKEY,
 VALUE_FROM LIKE YCACEDI-VALUE_FROM,
*<-- End of G9DK9A09ND
 NAME1 LIKE T001W-NAME1,
 COM_NAME LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 POST_LOC LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 CUST_OFFICE LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 POST_CODE LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 DATE(25),
 ETAB LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 NO_SIREN LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 TEXT2 LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 TEXT5 LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 TEXT7A LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 TEXT7B LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 TEXT8 LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 END OF TY_HEADER.
TYPES : BEGIN OF TY_DELIVERY,
 VBELN LIKE LIKP-VBELN,
 POSNR LIKE LIPS-POSNR, "G9DK961190
 VBUND LIKE LIKP-VBUND,
 LFIMG LIKE LIPS-LFIMG,
 MEINS LIKE LIPS-MEINS,
 EXNUM LIKE LIKP-EXNUM,
 KUNNR LIKE LIKP-KUNNR,
 KUNAG LIKE LIKP-KUNAG,
 L15 LIKE LIPS-LFIMG,
 WADAT_IST LIKE LIKP-WADAT_IST,
 LDDAT LIKE LIKP-LDDAT,
 NTGEW LIKE LIKP-NTGEW,
 MATNR LIKE MARA-MATNR,
 VRKME LIKE LIPS-VRKME, "G9DK960368
 VGBEL LIKE LIPS-VGBEL, "G9DK961190
 VGPOS LIKE LIPS-VGPOS, "G9DK961190
 UECHA LIKE LIPS-UECHA, "G9DK961190
 END OF TY_DELIVERY.
TYPES : BEGIN OF TY_INVOICE,
 ZDELN LIKE VBRK-VBELN,
 NETWR LIKE VBRK-NETWR,
 WAERK LIKE VBRK-WAERK,
 KURRF LIKE VBRK-KURRF,
 FKIMG LIKE VBRP-FKIMG,
 VRKME LIKE VBRP-VRKME,
 END OF TY_INVOICE.
TYPES : BEGIN OF TY_INVOICE_TEMP,
 ZDELN LIKE VBRK-VBELN,
 FKART LIKE VBRK-FKART,
 YY_SEQTAXNO LIKE VBRK-YY_SEQTAXNO,
 END OF TY_INVOICE_TEMP.
TYPES : BEGIN OF TY_EXPORT,
 EXNUM LIKE EIKP-EXNUM,
 ZOLLA LIKE EIKP-ZOLLA,
 STGBE LIKE EIKP-STGBE,
 EXPVZ LIKE EIKP-EXPVZ,
 CONTA LIKE EIKP-CONTA,
 IEVER LIKE EIKP-IEVER,
 EXPRF LIKE EIPO-EXPRF,
 EXART LIKE EIPO-EXART,
 EXPOS LIKE EIPO-EXPOS, "G9DK961190
 STAWN LIKE EIPO-STAWN, "G9DK961190
 END OF TY_EXPORT.
TYPES : BEGIN OF TY_HFILE,
 POS1(8),
 POS2(4),
 POS3(2),
 POS4,
 POS5(8),
 POS6(4),
 POS7(14),
 POS8(20),
 POS9(20),
 POS10(20),
 POS11(8),
 END OF TY_HFILE.
TYPES : BEGIN OF TY_DFILE,
 pos1(18), "G9DK961418
 POS1(19), "G9DK961418
 POS1(18), "G9DK962238
 POS2(4),
 POS3(8),
 POS4(6),
 POS5(6),
 POS5A(4),
 POS6(9),
 POS6A(5), "G9DK962238
 POS7(5),
 POS8(5),
 POS8A(22),
 POS9,
 POS10,
 POS11,
 POS12,
 POS13(5),
 POS13A,
 POS14(13),
 POS14A(31),
 POS15(2),
 POS16(2),
 POS16A(3),
 POS17(4),
 POS17A(3),
 POS18(3),
 POS18A(9), "G9DK962238
 POS19,
 POS20(11),
 POS21(11),
 POS22(10),
 POS23(10),
 POS23A(40),
 POS24(4),
 POS25(3),
 POS26,
 POS26A,
 POS27,
 POS28(3),
 POS29,
 END OF TY_DFILE,
 BEGIN OF TY_TVKO, "G9DK959869
 VKORG LIKE TVKO-VKORG, "G9DK959869
 BUKRS LIKE TVKO-BUKRS, "G9DK959869
 KUNNR LIKE TVKO-KUNNR, "G9DK959869
 END OF TY_TVKO. "G9DK959869
 D A T A *
DATA: GV_CUST_NUM LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 GV_SIREN LIKE YSDA_DOC_FIXTEXT-YY_TEXT,
 GV_REP_NO LIKE YSDA_DOC_NUMBER-YY_PRINT_NO,
 GV_SEQ_NO TYPE I VALUE 0,
 GV_PRNTER LIKE TSP01-RQDEST, "Printer Name
 GV_DATE(8) TYPE C, "DATE
 GV_MONTH(2) TYPE C, "MONTH
 GV_DAY(2) TYPE C, "DAY
 GV_YEAR(4) TYPE C, "YEAR
 GV_ADD1(30) TYPE C, "TEXT-SIMBOL H01A
 GV_ADD2(30) TYPE C, "TEXT-SIMBOL H01B
 GV_COUNT TYPE I, "COUNT SEQUENCE
 GV_SEQUENCE(5) TYPE C, "SEQUENCE
 GV_COPYNO TYPE C, "NUMBER OF COPY
 GV_DATETEMP(10) TYPE C, "DATE
 GV_SECTIONPAGE(2) TYPE C, "NO. OF PAGE IN SECTION
 GV_ITEM TYPE I, "NO. OF ITEM
 GV_EUR LIKE VBRK-WAERK VALUE 'EUR',
 GV_INVOICE_NO LIKE VBRK-VBELN, "G9DK959869
 GV_INVOICE_INTERCOM LIKE VBRK-VBELN, "G9DK959869
 GV_PRO_FORMA_STO LIKE VBRK-VBELN, "G9DK969466
 GV_TEXT46 LIKE YSDA_DOC_FIXTEXT-YY_TEXT. "G9DK959869
 C O N S T A N T S *
CONSTANTS: GC_M VALUE 'M',
 GC_J VALUE 'J',
 GC_C VALUE 'C',
 GC_D VALUE 'D',
 GC_E VALUE 'E',
 GC_F VALUE 'F',
 GC_U VALUE 'U',
 GC_X VALUE 'X',
 GC_0 VALUE '0',
 GC_2 VALUE '2',
 GC_3 VALUE '3',
 GC_MEXP(4) VALUE 'MEXP',
 GC_ZAAD(4) VALUE 'ZAAD',
 GC_ZSAD(4) VALUE 'ZSAD',
 GC_CY(2) VALUE 'CY',
 GC_M1(2) VALUE 'M1',
 GC_M2(2) VALUE 'M2',
 GC_M4(2) VALUE 'M4',
 GC_M5(2) VALUE 'M5',
 GC_M6(2) VALUE 'M6',
 GC_M7(2) VALUE 'M7',
 GC_M8(2) VALUE 'M8',
 GC_M9(2) VALUE 'M9',
 GC_C3(2) VALUE 'C3',
 GC_00(2) VALUE '00',
 GC_C1(2) VALUE 'C1',
 GC_C2(2) VALUE 'C2',
 GC_SI(2) VALUE 'SI',
 GC_N1(2) VALUE 'N1',
 GC_N2(2) VALUE 'N2',
 GC_FR(2) VALUE 'FR',
 GC_EN(2) VALUE 'EN',
 GC_TON LIKE T006-MSEHI VALUE 'TO',
 GC_L15 LIKE T006-MSEHI VALUE 'L15',
 GC_GRWR(4) VALUE 'GRWR',
 GC_SAISUNIC(8) VALUE 'SAISUNIC',
 GC_000000(6) VALUE '000000',
 GC_1 VALUE '1', "G9BK900812
 GC_1 LIKE PLFH-MGVGW VALUE '1', "G9BK900812
 GC_DOT(1) VALUE '.',
 GC_TYP_EU(3) TYPE C VALUE 'EU ',
 GC_TYP_EX(3) TYPE C VALUE 'EX ',
 GC_TYP_COM(3) TYPE C VALUE 'COM',
 GC_BIS(3) TYPE C VALUE 'BIS',
 GC_EUR(3) TYPE C VALUE 'EUR',
 GC_IV(2) TYPE C VALUE 'IV',
 GC_ZTDR(4) TYPE C VALUE 'ZTDR',
 GC_ZF8(3) TYPE C VALUE 'ZF8',
 GC_ZIV(3) TYPE C VALUE 'ZIV',
 GC_FALSE(1) TYPE C VALUE ' ', "yuie
 GC_STRUCT(31) TYPE C VALUE 'DATA', "yuie
 GC_TOTAL TYPE VTXTM VALUE 'TOTAL NET UNIT PRICE',"G9DK960368
 GC_INTER_PERCENT TYPE VTXTM VALUE 'Inter-company %'."G9DK960368
 I N T E R N A L T A B L E S *
DATA: BEGIN OF IT_DOC OCCURS 0,
 VBELN LIKE LIKP-VBELN,
 FKART LIKE VBRK-FKART,
 ERDAT LIKE VBFA-ERDAT,
 ERZET LIKE VBFA-ERZET,
 ZDELN LIKE VBRK-VBELN,
 END OF IT_DOC,
 BEGIN OF IT_VBRK OCCURS 0,
 ZDELN LIKE VBRK-VBELN,
 END OF IT_VBRK,
 BEGIN OF IT_SALES OCCURS 0,
 VBELN LIKE LIKP-VBELN,
 VBELV LIKE VBAK-VBELN, "Order Number
 AUART LIKE VBAK-AUART,
 KNUMV LIKE VBAK-KNUMV,
 KALSM LIKE VBAK-KALSM, "G9DK960368
 WAERK LIKE VBAK-KALSM, "G9DK960368
 KNUMA LIKE VBAK-KNUMA, "G9DK960368
 END OF IT_SALES,
*--> begin of G9DK961190 kxumnauy 13 feb 2004
 BEGIN OF IT_VBAP OCCURS 0,
 VBELN LIKE VBAK-VBELN, " Sale doc.
 POSNR LIKE VBAP-POSNR, " Sales document item
 KNUMV LIKE VBAK-KNUMV, " No. of the document cond.
 KALSM LIKE VBAK-KALSM,
 WAERK LIKE VBAK-KALSM,
 KNUMA LIKE VBAK-KNUMA,
 END OF IT_VBAP,
*<-- end of G9DK961190
 BEGIN OF IT_KSCHL OCCURS 0,
 KNUMV LIKE KONV-KNUMV,
 KBETR LIKE KONV-KBETR,
 WAERS LIKE KONV-WAERS, "G9DK960368
 END OF IT_KSCHL,
 BEGIN OF IT_VBKD OCCURS 0,
 VBELV LIKE VBAK-VBELN,
 INCO1 LIKE VBKD-INCO1,
 END OF IT_VBKD,
 BEGIN OF IT_COUNTRY OCCURS 0,
 KUNNR LIKE KNA1-KUNNR,
 LAND1 LIKE KNA1-LAND1,
 END OF IT_COUNTRY,
 BEGIN OF IT_CNO OCCURS 0,
 HEADER_TYP LIKE YSDA_EXP_PRTLOG-YY_HEADER_TYP,
 INTERNAL_NO LIKE YSDA_EXP_PRTLOG-YY_INTERNAL_NO,
 PRINT_DATE LIKE YSDA_EXP_PRTLOG-YY_PRINT_DATE,
 INVOICE_AMT LIKE YSDA_EXP_PRTLOG-YY_INVOICE_AMT,
 CURRENCY LIKE YSDA_EXP_PRTLOG-YY_CURRENCY,
*-->Begin of G9DK9A09ND -VSRKODA -16/07/2007
 PLANT LIKE YSDA_EXP_PRTLOG-YY_PLANT,
*<--End of G9DK9A09ND
 END OF IT_CNO,
 BEGIN OF IT_LNO OCCURS 0,
 HEADER_TYP LIKE YSDA_EXP_PRTLOG-YY_HEADER_TYP,
 INTERNAL_NO LIKE YSDA_EXP_PRTLOG-YY_INTERNAL_NO,
 PRINT_DATE LIKE YSDA_EXP_PRTLOG-YY_PRINT_DATE,
 INVOICE_AMT LIKE YSDA_EXP_PRTLOG-YY_INVOICE_AMT,
 CURRENCY LIKE YSDA_EXP_PRTLOG-YY_CURRENCY,
*-->Begin of G9DK9A09ND -VSRKODA -16/07/2007
 PLANT LIKE YSDA_EXP_PRTLOG-YY_PLANT,
*<--End of G9DK9A09ND
 END OF IT_LNO,
 BEGIN OF IT_LINV OCCURS 0,
 HEADER_TYP LIKE YSDA_EXP_PRTLOG-YY_HEADER_TYP,
 INTERNAL_NO LIKE YSDA_EXP_PRTLOG-YY_INTERNAL_NO,
 PRINT_DATE LIKE YSDA_EXP_PRTLOG-YY_PRINT_DATE,
 INVOICE_AMT LIKE YSDA_EXP_PRTLOG-YY_INVOICE_AMT,
 CURRENCY LIKE YSDA_EXP_PRTLOG-YY_CURRENCY,
*-->Begin of G9DK9A09ND -VSRKODA -16/07/2007
 PLANT LIKE YSDA_EXP_PRTLOG-YY_PLANT,
*<--End of G9DK9A09ND
 EX_RATE LIKE YSDA_EXP_PRTLOG-YY_EX_RATE,
 LFIMG LIKE LIPS-LFIMG,
 ZDELN LIKE VBRK-YY_SEQTAXNO,
 END OF IT_LINV,
 BEGIN OF IT_DIFF OCCURS 0,
 HEADER_TYP LIKE YSDA_EXP_PRTLOG-YY_HEADER_TYP,
 VBELV LIKE VBAK-VBELN,
 INTERNAL_NO LIKE YSDA_EXP_PRTLOG-YY_INTERNAL_NO,
 PRINT_DATE LIKE YSDA_EXP_PRTLOG-YY_PRINT_DATE,
 INVOICE_AMT LIKE YSDA_EXP_PRTLOG-YY_INVOICE_AMT,
 CURRENCY LIKE YSDA_EXP_PRTLOG-YY_CURRENCY,
*-->Begin of G9DK9A09ND -VSRKODA -16/07/2007
 PLANT LIKE YSDA_EXP_PRTLOG-YY_PLANT,
*<--End of G9DK9A09ND
 EX_RATE LIKE YSDA_EXP_PRTLOG-YY_EX_RATE,
 LFIMG LIKE LIPS-LFIMG,
 NETWR LIKE VBRK-NETWR,
 WAERK LIKE VBRK-WAERK,
 KURRF LIKE VBRK-KURRF,
 FKIMG LIKE VBRP-FKIMG,
 ZDELN LIKE VBRK-YY_SEQTAXNO,
 END OF IT_DIFF.
*-->Begin of G9DK9A09ND -VSRKODA -09/07/2007
Data :Begin of it_t001k occurs 0,
 bwkey like t001k-bwkey,
 bukrs like t001k-bukrs,
 werks like t001w-werks,
 end of it_t001k.
TABLES: T001W.
Data :Begin of it_t001w occurS 0,
 bwkey like t001w-bwkey,
 werks like t001w-werks,
 end of it_t001w.
*<-- End of G9DK9A09ND
*-->Begin of G9DK9A09ND -VSRKODA -09/07/2007
DATA: BEGIN OF IT_SIREN OCCURS 0,
 VALUE_FROM LIKE YCACEDI-VALUE_FROM,
 MESTYP LIKE YCACEDI-MESTYP,
 DIRECT LIKE YCACEDI-MESTYP,
 ORG_LEVEL LIKE YCACEDI-ORG_LEVEL,
 ORG_VALUE LIKE YCACEDI-ORG_VALUE,
 FIELDNAME LIKE YCACEDI-FIELDNAME,
 END OF IT_SIREN.
*<-- End of G9DK9A09ND
*--> Begin of G9DK959869 KXSAWAS 02/02/2004
DATA: BEGIN OF IT_ORDER OCCURS 0,
 VBELN LIKE VBAK-VBELN, " Order no.
 VKORG LIKE VBAK-VKORG, " Sale Org. of order
 END OF IT_ORDER,
 BEGIN OF WA_T001W,
 WERKS LIKE T001W-WERKS, " Plant
 BUKRS LIKE T001K-BUKRS,
*-->Begin of G9DK9A09ND -VSRKODA -09/07/2007
 BWKEY LIKE T001K-BWKEY,
*<-- End of G9DK9A09ND
 VKORG LIKE T001W-VKORG, " Sale Org. of plant
 COUNC LIKE T001W-COUNC, " Country code
 LAND1 LIKE T001W-LAND1, "
 ADRNR LIKE T001W-ADRNR,
 ORT01 LIKE T001W-ORT01,
 END OF WA_T001W,
 BEGIN OF IT_LIKP OCCURS 0,
 VBELN LIKE LIKP-VBELN, " Delivery
 VKORG LIKE LIKP-VKORG, " Sale organization
 KUNNR LIKE LIKP-KUNNR, " Ship-to party
 INCO1 LIKE LIKP-INCO1, " Incoterm part1
 INCO2 LIKE LIKP-INCO2, " Incoterm part2
 END OF IT_LIKP.
*<-- End of G9DK959869
DATA: IT_RAW TYPE TABLE OF TY_RAW WITH HEADER LINE,
 IT_DATA TYPE TABLE OF TY_DATA WITH HEADER LINE,
 IT_EXPORT TYPE TABLE OF TY_EXPORT WITH HEADER LINE,
 IT_DELIVERY TYPE TABLE OF TY_DELIVERY WITH HEADER LINE,
 IT_INVOICE TYPE TABLE OF TY_INVOICE WITH HEADER LINE,
 IT_FILE TYPE TABLE OF TY_DFILE WITH HEADER LINE,
 IT_HEADER TYPE TABLE OF TY_HEADER WITH HEADER LINE,
 IT_SELTAB TYPE TABLE OF RSPARAMS WITH HEADER LINE,
 IT_INVOICE_TEMP TYPE TABLE OF TY_INVOICE_TEMP WITH HEADER LINE,
 IT_TVKO_ORDER TYPE TABLE OF TY_TVKO WITH HEADER LINE,"G9DK959869
 IT_DEL TYPE TABLE OF TY_DELIVERY WITH HEADER LINE. "G9DK960368
*--> Begin of G9DK960368 KXSAWAS 05/02/2004
DATA: BEGIN OF YUIE_ITAB OCCURS 0,
 RECID(31),
 DATA(1024).
DATA: END OF YUIE_ITAB.
TYPE-POOLS: YUIEX.
*DATA : it_komv2 LIKE komv OCCURS 0 WITH HEADER LINE. "G9DK961190
*<-- End of G9DK960368
*Begin of G9DK964590 kxumnauy 30 mar 2003
DATA: BEGIN OF KEY_ZBAT01,
 MANDT TYPE ZBAT01-MANDT,
 REPID TYPE ZBAT01-REPID,
 FUNCT TYPE ZBAT01-FUNCT,
 END OF KEY_ZBAT01.
*End of G9DK964590
*--> Begin of G9DK968994 kxumnauy
DATA: BEGIN OF IT_INVOICE_ITEM OCCURS 0,
 VBELN LIKE VBRP-VBELN,
 POSNR LIKE VBRP-POSNR,
 NETWR LIKE VBRP-NETWR,
 VGBEL LIKE VBRP-VGBEL,
 VGPOS LIKE VBRP-VGPOS,
 MATNR LIKE VBRP-MATNR,
 fkimg LIKE VBRP-fkimg, "G9DK969188
 vrkme LIKE VBRP-vrkme, "G9DK969188
 ntgew LIKE VBRP-ntgew, "G9DK969188
 gewei LIKE VBRP-gewei, "G9DK969188
 END OF IT_INVOICE_ITEM.
*<-- End of G9DK968994
RANGES: S_LAST FOR SY-DATUM,
 S_PERIOD FOR SY-DATUM.
 W O R K A R E A S *
DATA: WA_RAW TYPE TY_RAW,
 WA_DATA TYPE TY_DATA,
 WA_EXPORT TYPE TY_EXPORT,
 WA_DOC LIKE IT_DOC,
 WA_SALES LIKE IT_SALES,
 WA_SALES1 LIKE IT_SALES, "G9DK972875
 WA_KSCHL LIKE IT_KSCHL,
 WA_VBKD LIKE IT_VBKD,
 WA_COUNTRY LIKE IT_COUNTRY,
 WA_DELIVERY TYPE TY_DELIVERY,
 WA_INVOICE TYPE TY_INVOICE,
 WA_LINV LIKE IT_LINV,
 WA_CNO LIKE IT_CNO,
 WA_LNO LIKE IT_LNO,
 WA_DIFF LIKE IT_DIFF,
 WA_HEADER TYPE TY_HEADER,
 WA_VBRK LIKE IT_VBRK,
 WA_FILE TYPE TY_DFILE,
 WA_HFILE TYPE TY_HFILE,
 WA_SELTAB TYPE RSPARAMS,
 WA_INVOICE_TEMP TYPE TY_INVOICE_TEMP,
 WA_TVKO_PLANT TYPE TY_TVKO, "G9DK959869
 WA_LIKP LIKE IT_LIKP, "G9DK959869
 WA_DEL LIKE IT_DELIVERY, "G9DK960368
 WA_KOMK LIKE KOMK, "G9DK960368
*-->Begin of G9DK9A09ND -VSRKODA -09/07/2007
 WA_T001K LIKE T001K.
*<-- End of G9DK9A09ND
 S E L E C T - O P T I O N S / P A R A M E T E R S *
SELECTION-SCREEN BEGIN OF BLOCK SCR1 WITH FRAME TITLE TEXT-001.
*Begin of change VSRKODA
PARAMETERS: P_BUKRS LIKE T001K-BUKRS,
 S_WERKS LIKE T001W-WERKS,
*end of change VSRKODA
 P_MNR LIKE T247-MNR,
 P_YEAR LIKE VBRK-GJAHR.
SELECT-OPTIONS: S_WERKS FOR T001W-WERKS.
PARAMETERS: P_PRNTER LIKE TSP01-RQDEST. "Printer Name
 p_file AS CHECKBOX. "yuie
SELECTION-SCREEN END OF BLOCK SCR1.
*--> Begin of G9DK960368 KXSAWAS 05/02/2004
*--- Comment out ---
*SELECTION-SCREEN BEGIN OF BLOCK b2
 WITH FRAME TITLE text-t01.
*PARAMETERS: p_fname LIKE rlgrap-filename .
*SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-T01.
PARAMETERS: P_FILE AS CHECKBOX.
PARAMETERS: P_FNAME TYPE EPSFILNAM LOWER CASE, "interface UNIX file
 P_SPATH TYPE EPSDIRNAM DEFAULT
 '/opt/mobil/batch/gem/other/common/data/' LOWER CASE.
SELECTION-SCREEN END OF BLOCK B2.
SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME TITLE TEXT-T03.
PARAMETERS: P_INTID TYPE YINT_IDS DEFAULT 'DCG_REPORT',
 P_SUBID TYPE YINT_SUB_IDS DEFAULT 'MAIN'.
SELECTION-SCREEN END OF BLOCK B3.
*<-- End of G9DK960368
AT SELECTION SCREEN
AT SELECTION-SCREEN.
To validate the data that user entered in the selection screen
PERFORM F_VALIDATE_DATA.
PERFORM F_GET_COMPANY_CODE.
 I N I T I A L I Z A T I O N *
INITIALIZATION.
P_MNR = SY-DATUM+4(2).
P_YEAR = SY-DATUM+0(4).
*--> Begin of G9DK960368 KXSAWAS 05/02/2004
*---Set default unix file name yuie
CONCATENATE 'DCG_SAISUNIC' SY-UNAME
 INTO P_FNAME
 SEPARATED BY '_'.
*<-- End of G9DK960368
 B E G I N - O F - S E L E C T I O N *
START-OF-SELECTION.
GV_PRNTER = P_PRNTER.
PERFORM F_INIT_PERIOD.
PERFORM F_GET_CURRENT_REPORT_NUMBER.
PERFORM F_GET_COMPANY_CODE.
PERFORM F_EXTRACT_RAW_DATA.
PERFORM F_PROCESS_DATA.
IF SY-BATCH EQ GC_X.
 PERFORM F_UPDATE_REPORT_NUMBER.
ENDIF.
END-OF-SELECTION.
IF NOT ( IT_HEADER[] IS INITIAL AND IT_DATA[] IS INITIAL AND
 IT_CNO[] IS INITIAL AND IT_LNO[] IS INITIAL AND
 IT_LINV[] IS INITIAL AND IT_DIFF[] IS INITIAL ).
 PERFORM F_PRINT_ACCELIO.
ELSE.
 MESSAGE ID 'YM' TYPE 'I' NUMBER '032' "G9DK961073
 WITH 'No data found for entered criteria'(E01).
 EXIT.
ENDIF.
*If run by batch job print invoice
IF SY-BATCH EQ GC_X.
 PERFORM F_PRINT_INVOICE.
ENDIF.
 B E G I N O F F O R M *
*& Form F_INIT_PERIOD
 Period
FORM F_INIT_PERIOD.
DATA: LV_FIRST LIKE SY-DATUM,
 LV_CURRENT LIKE SY-DATUM,
 LV_LAST LIKE SY-DATUM,
 LV_DTEMP_FIRST(12) TYPE C,
 LV_DTEMP_LAST(12) TYPE C.
LV_FIRST+0(4) = P_YEAR.
LV_FIRST+4(2) = P_MNR.
LV_FIRST+6(2) = '01'.
LAST DAY OF CURRENT MONTH
CALL FUNCTION 'LAST_DAY_OF_MONTHS'
 EXPORTING
 DAY_IN = LV_FIRST
 IMPORTING
 LAST_DAY_OF_MONTH = LV_CURRENT
 EXCEPTIONS
 DAY_IN_NO_DATE = 1
 OTHERS = 2.
IF SY-SUBRC = 0.
 IF P_MNR < '2'.
 LV_FIRST+0(4) = P_YEAR - 1.
 LV_FIRST+4(2) = '12'.
 LV_FIRST+6(2) = '01'.
 ELSE.
 LV_FIRST+0(4) = P_YEAR.
 LV_FIRST+4(2) = P_MNR - 1.
 LV_FIRST+6(2) = '01'.
 ENDIF.
LAST DAY OF LAST MONTH
 CALL FUNCTION 'LAST_DAY_OF_MONTHS'
 EXPORTING
 DAY_IN = LV_FIRST
 IMPORTING
 LAST_DAY_OF_MONTH = LV_LAST
 EXCEPTIONS
 DAY_IN_NO_DATE = 1
 OTHERS = 2.
 IF SY-SUBRC = 0.
 LV_FIRST = '20040101'. "G9DK973032
LAST MONTH
 S_LAST-SIGN = 'I'.
 S_LAST-OPTION = 'BT'.
 S_LAST-LOW = LV_FIRST.
 S_LAST-HIGH = LV_LAST.
 APPEND S_LAST.
LAST MONTH AND CURRENT MONTH
 S_PERIOD-SIGN = 'I'.
 S_PERIOD-OPTION = 'BT'.
 S_PERIOD-LOW = LV_FIRST.
 S_PERIOD-HIGH = LV_CURRENT.
 APPEND S_PERIOD.
 ENDIF.
ENDIF.
ENDFORM. " F_INIT_PERIOD
*& Form F_GET_CURRENT_REPORT_NUMBER
 Get current Seq. no. from YSDA_DOC_NUMBER
FORM F_GET_CURRENT_REPORT_NUMBER.
DATA: LV_RC LIKE SY-SUBRC.
CHECK SY-BATCH = GC_X.
DO 3 TIMES.
 PERFORM F_LOCK_OBJECT CHANGING LV_RC.
 IF LV_RC <> 0.
 PERFORM F_WAIT.
 ELSE.
 EXIT.
 ENDIF.
ENDDO.
IF LV_RC <> 0.
 PERFORM F_UNLOCK_OBJECT.
 PERFORM F_LOCK_OBJECT CHANGING LV_RC.
ENDIF.
SELECT SINGLE YY_PRINT_NO
 INTO GV_REP_NO
 FROM YSDA_DOC_NUMBER
*-->Begin of G9DK9A09ND -VSRKODA -09/07/2007
 where yy_plant = P_WERKS
*<-- End of G9DK9A09ND
 WHERE YY_PLANT IN S_WERKS
 AND YY_YEAR = P_YEAR
 AND YY_DOCUMENT_CODE = GC_MEXP.
*--> Begin of G9DK959869 KXSAWAS 02/02/2004
IF SY-BATCH = GC_X.
 GV_REP_NO = GV_REP_NO + 1.
ELSE.
 GV_REP_NO = 0.
ENDIF.
*<-- End of G9DK959869
ENDFORM. " F_GET_CURRENT_REPORT_NUMBER
*& Form F_GET_COMPANY_CODE
 text
--> p1 text
<-- p2 text
FORM F_GET_COMPANY_CODE.
CLEAR: it_t001k-bwkey.
Validate input data against master table of SAP
Validate company code against T001k
IF NOT P_BUKRS IS INITIAL.
 SELECT T001K~BUKRS
 T001K~BWKEY
 T001W~WERKS
 INTO CORRESPONDING FIELDS OF TABLE IT_T001K
 FROM T001K
INNER JOIN T001W ON T001W~BWKEY = T001K~BWKEY
 WHERE BUKRS = P_BUKRS
 AND WERKS IN S_WERKS.
 APPEND IT_T001K.
 select t001kbukrs t001kbwkey t001w~werks
 into corresponding fields of table itab
 from t001w
 inner join t001k
 on t001kbwkey = t001wbwkey.
 LOOP AT IT_T001K.
 it_t001k-bwkey = it_t001w-werks.
 ENDLOOP.
ENDIF.
ENDFORM. " F_GET_COMPANY_CODE
*& Form F_EXTRACT_RAW_DATA
 Extract entries from YSDA_EXP_PRTLOG
FORM F_EXTRACT_RAW_DATA.
SELECT YY_PLANT
 YY_HEADER_TYP
 YY_INTERNAL_NO
 YY_PRINT_DATE
 YY_PRINT_TIME
 YY_DOCUMENT_CODE
 YY_HEADER_TYP
 YY_DELIVERY
 YY_INVOICE_AMT
 YY_EX_RATE
 YY_CURRENCY
 YY_INTERNAL_NO "G9DK962238
 YY_EXTERNAL_NO
 YY_COMMODITY
 YY_REPORT_FLAG "G9DK962077
 INTO corresponding fields of TABLE IT_RAW
 FROM YSDA_EXP_PRTLOG
WHERE YY_PLANT IN S_WERKS
**-->Begin of G9DK9A09ND -VSRKODA -09/07/2007
 where yy_plant = s_werks
**<-- End of G9DK9A09ND
 and YY_PRINT_DATE IN S_PERIOD+
 AND YY_REPORT_FLAG <> 'X' "G9DK973032
 AND YY_HEADER_TYP <> 'T2L' "G9DK9A02DZ
 AND YY_ANNULATION <> 'X'.
*If run by batch job
*--> Begin of G9DK959869 KXSAWAS 02/02/2004
*--- Comment out ---
IF sy-batch EQ gc_x.
 IF NOT it_raw[] IS INITIAL.
 LOOP AT it_raw.
**Update YY_REPORT_FLAG EQ 'X'
 UPDATE ysda_exp_prtlog SET yy_report_flag = gc_x
 WHERE yy_plant = p_werks
 AND yy_print_date = it_raw-print_date
 AND yy_print_time = it_raw-print_time
 AND yy_document_code = it_raw-document_code.
 ENDLOOP.
 ENDIF.
ENDIF.
*<-- End of G9DK959869
LOOP AT IT_RAW.
 IT_RAW-HEADER_SHT = IT_RAW-HEADER_SHT+0(3).
 MODIFY IT_RAW.
ENDLOOP.
SORT IT_RAW BY WERKS HEADER_SHT INTERNAL_NO "G9DK962271
PRINT_DATE. "G9DK962238
ENDFORM. " F_EXTRACT_RAW_DATA
*& Form F_PROCESS_DATA
 Extract all required data
FORM F_PROCESS_DATA.
PERFORM F_EXTRACT_DOC_FLOW.
PERFORM F_EXTRACT_INCO_TERM.
PERFORM F_EXTRACT_DELIVERY_DATA.
PERFORM F_EXTRACT_INVOICE_DATA.
PERFORM F_EXTRACT_EXPORT_DATA.
PERFORM F_EXTRACT_HEADER_DATA.
PERFORM F_EXTRACT_COMPANY. "G9DK959869
PERFORM F_CLASSIFY_DATA.
ENDFORM. " F_PROCESS_DATA
*& Form F_EXTRACT_DOC_FLOW
 Extract Sale data
FORM F_EXTRACT_DOC_FLOW.
IF NOT IT_RAW[] IS INITIAL.
 SELECT VBELV
 VBTYP_N
 ERDAT
 ERZET
 VBELN
 INTO TABLE IT_DOC
 FROM VBFA
 FOR ALL ENTRIES IN IT_RAW
 WHERE VBELV = IT_RAW-DELIVERY
 AND ( VBTYP_N = 'M'
 OR VBTYP_N = '5' ).
 SELECT A~VBELN
 A~VBELV
 B~AUART
 B~KNUMV
 B~KALSM "G9DK960368
 B~WAERK "G9DK960368
 B~KNUMA "G9DK960368
 INTO TABLE IT_SALES
 FROM VBFA AS A INNER JOIN VBAK AS B
 ON AVBELV = BVBELN
 FOR ALL ENTRIES IN IT_RAW
 WHERE A~VBELN = IT_RAW-DELIVERY
 AND A~VBTYP_N = GC_J.
ENDIF.
SORT IT_SALES BY VBELN VBELV.
DELETE ADJACENT DUPLICATES FROM IT_SALES COMPARING ALL FIELDS.
SORT IT_DOC BY VBELN ASCENDING
 FKART ASCENDING
 ERDAT DESCENDING
 ERZET DESCENDING.
DELETE ADJACENT DUPLICATES FROM IT_DOC COMPARING ALL FIELDS.
IF NOT IT_SALES[] IS INITIAL.
 SELECT KNUMV
 KBETR
 WAERS "G9DK960368
 INTO TABLE IT_KSCHL
 FROM KONV
 FOR ALL ENTRIES IN IT_SALES
 WHERE KNUMV = IT_SALES-KNUMV
 AND KSCHL = GC_GRWR.
ENDIF.
SORT IT_KSCHL BY KNUMV.
ENDFORM. " F_EXTRACT_DOC_FLOW
*& Form F_EXTRACT_INCO_TERM
 Extract inco term
FORM F_EXTRACT_INCO_TERM.
IF NOT IT_SALES[] IS INITIAL.
 SELECT VBELN


What's wrong with F_GET_COMPANY_CODE ? Below is similar code - try running this and seeing what you get:
report zlocal_jc_t001w.
tables:
t001k, "Valuation area
t001w. "Plants/Branches
parameters:
p_bukrs like t001k-bukrs default '1000'.
select-options:
s_werks for t001w-werks.
start-of-selection.
perform get_data.
*& Form get_data
form get_data.
data:
 begin of gt_t001k occurs 10,
 bukrs like t001k-bukrs,
 bwkey like t001k-bwkey,
 werks like t001w-werks,
 end of gt_t001k.
select
 t001k~bukrs
 t001k~bwkey
 t001w~werks
 into corresponding fields of table gt_t001k
 from t001k as t001k
 inner join t001w as t001w on t001w~bwkey = t001k~bwkey
 where t001k~bukrs = p_bukrs
 and t001w~werks in s_werks.
loop at gt_t001k.
 write: /
 gt_t001k-bukrs,
 gt_t001k-bwkey,
 gt_t001k-werks.
endloop.
endform. "get_data
As for links to locally defined database tables, that will depend on what the keys defined in SE11 are e.g. there will be a primary key plus relationships to other tables (for example "WERKS LIKE YSDA_EXP_PRTLOG-YY_PLANT" indicates YY_PLANT relates to T001W).
Jonathan

Plant to Plant STO with excise invoice and taxes in one company code

Hi,
I have a new business requirement, we want to create only one company code and 12 plants in different states, each plant will have separate purchasing and sales activity this is ok this can be done with separate excise and series group as ther will not be any issue for purchsing and saling of materisl with exice in each plant , but how we can transfer the material plant to plant if the plant is in different states we want that the material should be transfer from palnt to plant with excise invoice only, as we have the company code common, how to create the billing document for this, and how to pass the duty from the saling plant and capture the same in the recieving plant. with proper tax entry. Can we do the STO with biiling if the two plants are in single compnay code.
regards,
zafar

hi,
I am trying to create a Stock Transport Order (STO) with document type UB and item category U. My objective is to transfer material from Plant (supplying plant) 100 to Plant (receiving plant) 1100 within one company code (1000) with STO.
For this purpose I created a raw material 1434 in plant 1000 with sales org 1 view and in that view entered in delivering plant field 1000 as delivery plant. After that I extended material 1434 to plant 1100 without changing anything what I did while creating the material first in Plant 1000 except in organizational level I entered 1100 in the plant field. I entered Sales org 1000 and distribution channel 10 in organization level for both plant while creating and extending the material. In me21n I chose Stock Transport Order with document type UB and item category as U also receiving Plant as 1100. With this when I tried to save the STO the message, I am getting an error, Cannot determine shipping data for the material 1434?
I am doing solely mm function why I need to create Customer master? In this case plant 1100 is the customer right?
Solution:
1. Mat.(1434) should be maintained in both the plants. (1000&1100).
2. Should have enough stock in supplying plant(1000).
3. Make its supplying plant as a vendor in vendor master record in receiving plant(1100).
4. Make it receiving plant as a customer in customization.
    Create customer (xd01) & and define the shipping data for plants in both the plants.
    Path: spro u2013 img u2013 m.mgmt u2013 purchasing u2013 po u2013 set up STO u2013 define shipping data (1 by1 )
    In Receiving plant (1100)                         In Supplying plant (1000)
    Customer num. 123345 (for ex.)              Customer num. -
(don't fill)
    Sales org.yyy
    Dist. Channel
    Sales div. y
5. Assign doc. Type is "NL" for intra company STO. If STO is inter company, Assign doc. Type is "NLCC".
    Position doc type is "UB"
    Enter supplying plant(1000) & doc type (NL) & checking rule (ex:01)
6. Assign doc. Type is "UB" to u'r plants.(PO)
    Go for new entries
    Enter supplying plant(1000) & Receiving plant (1100) & doc type (UB).
7. Create a PO, choose the doc type is `UB' & item cat.'U', Enter supplying plant as a vendor in PO of the receiving plant(1100).
8. Provide this num (PO) to SD people, they will do the delivery by using transactional code is VL10B.
9. Sales people they will provide "out bound delivery num".
10. Do the GR. In GR the second tab 05 out bound delivery instead of PO mov.type 101.
11. See the stock over view in the receiving & supplying plants.
thanking you

Actual and Plan Versions annual view - Multiple versions per company code

Good Day,
Iu2019m creating an FI-CO query with an annual view of both Actuals and Plan Values, which uses period and version as input values. The dilemma is around the plan versions which are hardcoded per company codes (eg. 1 Company Code = versions 501 u2013 512)
Can anyone suggest a possible solutions as normally there is only one version used for planning but in this instance there are multiple versions per Company Code.
Currently the report is hardcoded for one Company Code and going forward it should cater for more than one(Company Company* 12 Version)
Kind Regards

Remove restriction on comp code. There could be 2 models.
1. Include comp code, value type and version in the rows. This way you get multiple records for a comp code. One record for actual data and one record each for plan versions. To have this model at the query, the data model in the cube also should be in this way (what we call as the account model), multiple records differentiated into actual/plan by valuetype and different versions by version.
2. Include comp code in rows. Create selections, one for actuals (restrict with key fig and value type 10, actuals), one for each plan versions (restrict key fig with value type 20, version 501. Create one selection for each version this way). This way we have one record per comp code with diff key fig for actual and plan versions. We call this as key fig model. To have this model at the query, the data model in the cube could be account model or key fig model. If it is key fig model then no need of selections. The key fig could be taken directly from the cube.

BP search for General and Company Code roles

Hi
On the modify Money Market Transactions (TM_52) (and some similar to it for other products TS02, TM32, TO02), if i go to the Partner Assignment Tab and I try to assign a bp for the General or the Company Code roles, the bp search program give me no results.
If i try to do the search for the Counterparty role it gives me the results I expect.
Is there any reason for do not give any result when these roles are the primary roles that, of course, the bp I choose has? Is it a program problem (this program has returned me some dumps and I implemented some Notes on it before)? If so, is there any solution?
I want to assign these roles because I hope that these assignments with these roles modify the payment data or the master data of the transaction.
Thanks

Hi
This is a very common topic.
look at this thread:
Authorization in reports
Here's a starting point ...
http://help.sap.com/saphelp_bw33/helpdata/en/72/eeb23b94c6e54be10000000a11402f/frameset.htm
Outline steps...
In RSSM:
Create authorization object
Make authorization object applicable to relevant InfoProviders
In PFCG:
Add authorization object to new or existing Roles with appropriate field assignments
Make User/Role assignments
Reg's
Edan

Payroll Posting to multiple Company Codes in FI and CO possible?

Dear experts,
I need your help on the following challenging issue with respect to payroll posting to accounting.
Is it possible for a payroll that runs in one company code for all employees, to post to FI and CO for multiple CoCds?
Example:
WT 1234 exists in HR CoCd 1000 (assume an amount of u20AC 100 in the payroll results)
G/L ABC exists in FI CoCd 1000
G/L DEF exists in FI CoCd 2000
CCtr xyz exists in CO CoCd 1000 (which is the employee's master cost centre)
CCtr uvw exists in CO CoCd 2000
The wage type should be mapped as follows:
+ 100 to G/L ABC and CCtr xyz (this is no problem, is realized with standard mapping)
- 100 to G/L DEF and CCtr uvw
The challenge is in the fact that the credit amount should go to another company code than the debit amount.
How can I realize this?
Thanks in advance for your feedback!
Jeroen

This is from SAP documentation:
Cross-company code transactions are characterized by the fact that payables are assigned to a company code other than the one in which the corresponding expenses arose. This results in receivables and payables between company codes.
If you want to post these receivables and payables to company code clearing accounts, you must make the settings in several steps, as outlined in the following.
Note that in the case of separate HR/AC systems, posting to company code clearing accounts can only be implemented if the AC system is in Release 4.5A or higher.
For more information on cross-company code transactions and business considerations, refer to the SAP Library under Payroll -> country -> Subsequent Activities -> Posting to Accounting -> Special Business Requirements for Posting -> Cross-Company Code Transactions.
Settings for Posting to Company Code Clearing Accounts
1. In the step Define Symbolic Accounts, you must assign an account determination type to each symbolic account in Human Resources. For specific postings to balance sheet accounts, the account assign types FL and FO are used. From a technical viewpoint, these account assignments are defined as follows:
Wage types that are assigned to a symbolic account with account assignment type FL are posted in accordance with the information from the last period in the WPBP table (Work Center Basic Pay) for the current original result.
Wage types that are assigned to a symbolic account with account assignment type FO are only used for posting in the evaluation of a current original result.
2. In the step Define Posting Characteristics of Wage Types, you must assign the symbolic accounts with the account assignment types FL and FO to the corresponding wage types:
You assign the symbolic accounts with account assignment type FL to wage types that, in the case of retroactive accounting, contain the difference between old and new payment amounts. In countries that use the principle of origin, this usually involves wage types /551 Recalculation difference and /552 Subsequent clearing from previous month.
You assign symbolic accounts with the account assignment type FO to wage types that contain payments to employees and whose amounts do not change in the case of retroactive accounting. This usually involves wage types /557 Cash payment, /558 Payment of balance, /559 Transfer and other, country-specific wage types.
3. In the step Create Posting Variants, you must set the Post to company-code clearing account indicator for the variants that you use. Otherwise, payables and receivables between company codes are not posted to company code clearing accounts, and remain as the balance on the document split account for the company codes affected.

Posting only possible in periods 2002/03 and 2002/02 in company code 0001

All
This is in the ongoing sequence where I am creating everything from the scratch(customers, material, prices etc).So far, I have been able to create and save the salesorder>deliver it>pick the items and then I was going to carry out the PGI and then this happened.
when I use the date i.e(Planned GI) 27-09-2006, I receive the following error
****************snip********************
Goods movement: Error log
Item   Material           Description                                   Delivery qty UoM Batch
000010 9                  T-AS1_MATERIAL__9                                      10 PC
       E M7 053
       Posting only possible in periods 2002/03 and 2002/02 in company code 0001
************End snip*********************
If I use a date as R/3 wants ,say 27.02.2002(Planned GI),I get:-
"Picking date is after goods issue date"...which is obvious.
any day after 27-09-2006, say 28-09-2006(Planned GI), I get :-
"Goods issue date is later than delivery date"...makes sence too
one thing was clear here to me, I can only post in Feb/March 2002, while my delivery date is 27 Sept 2006 . So I am in a classic chicken-egg situation.
where and who is giving this "Posting only possible in periods 2002/03 and 2002/02 in company code 0001" message ? How can I override this thing from the past ?
I thought of playing it smart and change my system date to the year Feb. 2002 , but in the fear that a lot of other things will fall as a result of that, I did refrain from doing so.
Could someone make this PGI succesful for me
Thanks for any lessons.

Thanks Mr. Srinivas
MMPV was indeed the magic wand.
PGI was successful.
this is my overall document flow as of now :-
Standard Order 2                                27.09.06 Completed
. Outbound delivery 80000000                    27.09.06 Completed
.. WMS transfer order 1                         29.09.06 Completed
.. GD goods issue:delvy 4900000020              30.09.06 complete
.. Invoice 90000000                             30.09.06 Missing export data
As I understand, my invoicing is not yet complete , it's got a number and got saved, but how shall I get rid of that red line message "Missing export data"(foriegn trade data incomplete...was the message while saving the billing document).I would be darn happy if I could just get rid of the foreign data part completely(just want to complete the invoice).Would this be checking off a mandatory rqmt. somewhere in the master data?
and would this also be the reason, why I see no accounting document which should have been on status 'open' by now ?
Thanks in advance ,

Company code and Purchase Org during vendor registration

Hi,
I have one enterprise context, with many company codes and purchasing org.
I am aware that vendor master data is at enterprise level in ESO. However while integrating to backend i need to capture the relevant co code and Purchasing org.
When the Purchaser wants to create a vendor, there does not seem anyway to enter which Purchasing org and company code the vendor should be created for.
Need your suggestions for the following options
1) capture co code and Purchasing org on bespoke fields and then in PI, pass these values to Co code and Purch org resp
2) create company contexts - would this resolve this? what are the implications if one vendor needs to be extended to multiple co codes
regards
Subrote

Hi,
Have you imported integration config workbook.
As part of ECC integartion guide we have couple of workbook and XML needs to integrated, which will create all the required extension for vendor master and vendor registration.
Once you imported the integration workbook, you will able to see the company code and purchasing org screens in vendor master.
Thank you,
Mani

Posting only possible in periods 2011/11 and 2011/10 in company code 4000

Hi All Experts,
I have encountered with this error while doing MIGO.
Posting only possible in periods 2011/11 and 2011/10 in company code 4000
Message no. M7053
Diagnosis
The posting date entered is not within one of the permitted posting periods (current period/previous period).
This can be due to one of two reasons:
The correct current period has not been set in the system.
For the system, the first of the entered periods is the current period. At the beginning of a new period, your systems administrator must change the current period in the material master record, using the function "Shift periods". This has not yet been done.
You have entered a wrong date in the field "Posting date".
Procedure
Check the posting date and correct it if necessary. If your input is correct, inform your systems administrator that the "period shifting" (period-end closing) process has not yet been completed.
I have checked OB52, OB29, OB37, MMPV, MMRV. All possible T.codes and threads I tried from SDN itself, still no luck ! In OB52 I have opened 2011 & 2012 year open absolute.
Would like to share MMRV settings :-
Current Period : 11 / 2011
Previous Period : 10 / 2011
Last period in prev year : 12 / 2010
We have India based client so fiscal year variant is Apr to March copied from V3.
Will be very much appreciable experts guidane !
Regards,
Sharvari Joshi.

Hi All Experts,
I raised the OSS, and here which I got the reply from SAP.
There is a possibility to run the report RMMMINIT to initialize posting
periods. Please bear in mind that the valuation data of the previous
period could get affected.
If you decide to proceed with the process, please review the
documentation of program RMMMINIT.
Please also review attached note 70545 regarding the initialization
process. Although this note is NOT valid for your release, it provides
good information on the use of initialization for correction purposes.
Additionally, please review attached note 369637 in this regard as well.
PLEASE FIRST PERFORM THIS IN A TEST/DEVELOPMENT SYSTEM PRIOR TO MOVING
TO PRODUCTION AS YOUR VALUATION DATA FROM PREVIOUS PERIOD WILL BE
AFFECTED. If you are satisfied with the results, then you can move it
to production. Please perform this at your own risk as this hotline
will not support any problems arising out of it.
Related the error message MM016 please follow the steps from note
487381:
To reserve the parameter use transaction SU01 for the user's name who
executes the RMMMINIT program. The parameter must be set as follows:
Parameter Value
MMPI_READ_NOTE YYYYMMDD (for the current date)
I am not able make out any meaning out of it. Can anyone please understand me this ?
Help will be appreciated !
Reagrds,
Sharvari Joshi.
P.S : Steps from my side which I performed , I changed the parameters for my ID in SU01 to current date 2011.11.16 (YYYYMMDD) and running MMPI still same error.

PO creation-ME21n-Why SAP does not check company code and Plant relation

Hi All,
Does someone know, why SAP does not check Plant and company code relation at the time of PO creation or how can we put validation between plant and company code at the time of PO creation.
Example: Suppose i have a company 0001 which is assinged to Plant 0001. when i am creating a PO with another company code 0002(Entering at header level-Org, data) and using Plant 0001 at line item level. SAP does not do this validation.
How can we put this check in place?
Thanks in advance.
Deepak

Hello Deepak,
There are three types of purchasing
- Company code specific :You need to assign company code to Pur organization
- Plant specific : You must assign plant to pur organization
- Cross company purchasing: No assignment between company code and pur organization.
In the case 3, the system will not check company code and plant relationship, but it will check plant and pur organization specific.
The following is the copy of sap help text:
You can assign a purchasing organization to one company code. This is company-specific purchasing.
You can assign a purchasing organization to no company code. This purchasing organization can then procure for all plants assigned to it, irrespective of the company code to which the plant belongs.
Since each plant must be assigned to a company code, the company code can be determined via the plant in each procurement transaction, even if the procuring purchasing organization is not assigned to a company code.
A purchasing organization must be assigned to one or more plants. This is plant-specific purchasing.
Now, check your company-code and purchase organization assignment.
Hope this helps.
Regards
Arif Mansuri

Authorization object for company code and profit center together

Hi all,
Please help me with the following requirement..
Company Code = ABCD
Profit Center = *
The user is authorized to run the report for company code ABCD only but any profit center within this company code.
2 Company Code = *
Profit Center = WXYZ
The user is authorized to run the report for Profit Center WXYZ only but any company code.
3 Company Code = *
Profit Center = *
The user is authorized to run the report for any company code and profit center.
The same user could have 1 and 2. So, in this case he should be able to run a report for the total inventory of company code ABCD, and a report for total inventory of profit center WXYZ only regardless company code.
He should not have visibility to other company codes inventory other then profit center WXYZ.
Regards,
Raj

Hi ,
Anyone please help me..
Regards,
Raj

Automatic creation of Company Code and Sales Area Data for Customer Master

Hi,
We have a organisation structure setup with multiple company codes and sales areas.
A customer will be created using VD01 via the Sales Order VA01. Because the customers are created using VD01 we need to automatically extend the customer for the various company codes and sales areas. The data on these views will be populated using reference customers.
Any recommendations on the best approach (technically) to auto extend the customer master would be appreciated.
I'm reluctant to use BDC's because of performance. We are in a Retail environment.
Thanks in advance
Craig

The sample code has been taken from the SAP notes - in which have the affected as outlined in the example.
The codes does not do what my requirements are, which is to identify the next available number in isolation of the BP type.

Default SC Plant Company code and Storage location Based on Position

Hi All,
We are on version SRM 7.02.
We are using SAP ECC R/3 EHP7 based system as a back end FI and HR system.
Org structure in SRM is replicated fromm HR system.
We have case of concurrent employment in the HR org structure , which means one USER can be assigned to multiple Positions in an org structure.
We have a user A , who is created in Two different org units say O1 , O2 occupying positions P1 and P2, belonging to company code C1 and C2.
Whenever a SC is created a custom enhancement shows all the user positions to him and he has to choose one from the list of positions.
Now based on the selected position(P1) , i have to default plant(PL1), storage location(SL1) and Company code(C1).
Even after defaulting attributes based on the position, user gets an error "company code C1 is not valid for user"
This error (Message class : /SAPSRM/CLL ; # 135) is thrown from method : /SAPSRM/CL_CH_WD_DODM_SC_I_BD /SAPSRM/IF_CLL_MAPPER~UPDATE
after getting user's Company code using following method.
/sapsrm/cl_pdo_shared_user=>/sapsrm/if_pdo_shared_user~get_company_code
This gets Company code as C2 ; Based on Users Attributes and not based on User Position attributes.
If i overwrite values fetched by this method in Implicit enhancement, then plant(PL1), storage location(SL1) are not getting fetched.
Does anyone have any solution for this problem?
Regards,
Ashish Shah

Hi MURUGESAN !
      Can you give me some information more in Special Procument Configure in plant 2000 like:
          - Procurement type (maybe F)
          - Special procurement (Maybe U)
          - Plant (Maybe 1000).
          - Issuing plant (maybe 2000)
       We will check together.
       Regards,
      Tony

Vendor Company Code and PO Company Code Different

HI All,
There is a central purch org for all comp code. Whenever we create a vendor we have to enter comp code, pur org and account grp. Suppose I create a vendor for Company Code "X" and another vendor for Company Code "Y". Pur Org will be same i.e. central pur org. Now I am creating a PO for Comp Code "X" but using vendor with Comp Code "Y". System is allowing me to create a PO in this way. I want the system should not allow me to create a PO in this way.
Even I have checked the message MEPO038, but I could not find this message
I am able to see the message ME038 is this the same.
Is it possible to advice me some user exits as well.
Thank you.
hani

Hi,
IF the vendor not created for that company code the system will throw error .this is the std functionality. In your case the vendor would have maintained for the both company code thats why it is allowing .
if you want to make MEPO038 as error message Create new entries as below
OLME ---Environmet data -- Attribute of system message click new entries
versio :00
App:MEPO
mess:038
cate: E
if you want use user exit try following
1.EXIT_SAPMM06E_012
2.BADI : ME_PROCESS_PO_CUST
method :Process_header or Check

How to find document attached to user and Company code?

Hi all,
Requirement: Select a list of Business documents ( Sales order/PO....) created or changed by specific users which belong to a Specific Company code.
ie,To develop a report which lists the Documents created/updated/changed based on specified date and users.
I think we can find from CDHDR & CDPOS tables. But i need to filter these documents or pick documents based on a Specific Company code.
ie.,from the list of records obtained from CDHDR table....how to filter these documents based on Company code......
valuable inputs needed.
Thanks,
Subba

Hi
Most of the application document Heade tables(VBAK,EKKO etc ) will have the field CRETAED by like ERNAM. and all these tables will have BUKRS field also in them
So compnay code wise User created documents list you will get.
Only problem is the Changed/Modified list by user with related Company code.
Anyhow you will get the User who changed the documents from CDPOS table.
But for linkthem to Company code I feel You need the
help of HR related Tables .
with the UNAME which you get from CDPOS table go to PA0105 infotype and get the PERNR linked with that user.
And get the attached BUKRS Company code from PA0001 infotype.
Hope this will solve your problem.
reward points if useful
regards
Anji

Company and company code

Similar Messages

Maybe you are looking for