EDI - Outbound Accounting Posting Journals to External System
Hi Experts,
I have a requirement in which I have to outbound
Accouting Journals to an external system...
Does standard SAP support such a functionality.
I looked at the outbound process code and was unable
to find anything on accounting. (which does make sense...) I also noticed that journal entry transactions such as FB01 do not have output controls like SD or MM.
Would I not be able to utilize standard idocs in this case?
Hi Rolmega,
Please refer the OSS note 616804 .That is exactly matching your requirement and guide you through out the development.
OSS note 616804.
Create a BAPI which can be used to create cash journal documents.
To do this, carry out the steps specified below in your system, or import the relevant Support Package.
1. In Transaction SE37, select the menu option 'Goto' -> 'Function Groups' -> 'Create group'. Create function group SAPLFCJ_BAPI with the short text 'BAPI for FI cash journal' and save it.
2. In Transaction SE37, create function module BAPI_CASHJOURNALDOC_CREATE in function group SAPLFCJ_BAPI in package CAJO with the short text 'Save FI cash journal documents' as a remote-enabled module.
a) Create the following function module documentation for the function module:
With BAPI BAPI_CASHJOURNALDOC_CREATE, you can save a document when you execute in the FI cash journal, in the same way as when you make an entry via the Interface Transaction FBCJ.
If the TESTRUN field is set, the system only carries out the checks and not the actual backup process when the database is updated.
If you want to save a cash journal document, the program that calls the BAPI has to execute the COMMIT WORK to update the document.
A document can contain several split rows.
You can post either expenses or receipts for each document. In other words, either the ITEMS-P_PAYMENTS or the ITEMS-P_RECEIPTS field has to be filled in all line items.
If the document contains several line items or entries in the control table, assigned net or tax base amounts are deleted.
The initiator has to assign the item number (ITEMS-POSITION_NUMBER) for all line items or for none.
If the initiator assigns one-time data, the item numbers (CPD_ITEMS-POSITION_NUMBER) have to correspond to the respective line item (ITEMS-POSITION_NUMBER). The same item number may be used in one one-time line item only.
If the extended withholding tax is active in the company code used, you can create only one line item and no split document for vendors or customers that are relevant for withholding tax.
The vendor has to be filled for all assigned rows of the withholding tax information (table WTAX_ITEMS).
If withholding tax information is to be assigned, the indicator for withholding tax type (WTAX_ITEMS-WTAXTYPE) has to be filled with a value that is defined in the vendor master record. In addition, the same indicator for the withholding tax type may be assigned in one line of the ITEMS table only. The system does not take into account the external item number for withholding tax information.
In the TAX_ITEMS table, the same tax code may be assigned in only one line.
If there are entries in the TAX_ITEMS table, every tax code or jurisdiction code of this table has to be assigned in at least one line of the ITEMS table or be able to be derived from the Customizing for the business transaction.
If, in Customizing, there are accounts and tax codes for interface transactions that are flagged as not ready for input, then the BAPI derives values that are transferred in the ITEMS table again and overwrites them if necessary.
A check recognizes that field HEADER-CHECK_NUMBER is filled when the BAPI is called.
You cannot use the BAPI to save a document in a cash journal if this cash journal is simultaneously blocked by another interface user or another BAPI initiator. When you execute the BAPI, the system also sets a block for other users.
The initiator of the BAPI can transfer additional field values via the EXTENSION_IN table and can process them further in a BADI called in the customer_function subroutine.
You cannot change saved documents or deposit checks.
a) Enter the following import parameters:
Parameter Name Type Associated Type Opt Pass Value Short text
HEADER LIKE BAPI_CJ_HEADER X Document header
Long text:
In the HEADER structure, you can assign the document header information of the cash journal document to be saved. Basically, the structure corresponds to the fields of the TCJ_DOCUMENTS table that are ready for input on the cash journal interface and which contain header information only.
TESTRUN LIKE BAPI2021_HELP X X Indicator for test run
TESTRUN without update
Long text:
If the TESTRUN field is set, the external structures transferred when the BAPI is called are assigned to the internal cash journal structures. The relevant checks are also carried out. However, no update occurs to save the document on the database.
b) Enter the following export parameters:
Parameter Name Type Associated Type Pass Value Short text
COMPANY_CODE LIKE BAPI_CJ_HEADER X Company code
-COMP_CODE
Long text:
The COMPANY_CODE parameter contains the company code of the saved cash journal document.
CASH_JOURNAL_NUMBER LIKE BAPI_CJ_HEADER Cash journal number
-CAJO_NUBMER
Long text:
The CASH_JOURNAL_NUMBER parameter contains the cash journal of the saved cash journal document.
FISCAL_YEAR LIKE BAPI_CJ_KEY X Fiscal year
-FISC_YEAR
Long text:
The FISCAL_YEAR parameter contains the fiscal year of the saved cash journal document, but it is only filled for check totals documents.
CASH_JOURNAL_DOC_NO LIKE BAPI_CJ_KEY X Document number
-POSTING_NUMBER cash journal document
Long text:
The CASH_JOURNAL_DOC_NO parameter contains the internal document number of the saved cash journal document.
c) Enter the following table parameters:
Parameter Name Type Associated Type Optional Short text
ITEMS LIKE BAPI_CJ_ITEMS Cash journal documentitems
Long text:
In the ITEMS table, you can assign the information for the line items of the cash journal document to be saved. Basically, the spaces in the table fields correspond to the fields of the TCJ_POSITIONS table that are ready for input on the cash journal interface and which contain item information only. You can assign several line items per document, in the same way as for the split lines that can be entered via the interface transaction.
TAX_ITMES LIKE BAPI_CJ_TAX_ITEMS X Cash journal tax items
Long text:
In the TAX_ITEMS table, you can assign tax information for the cash journal document to be saved. In this way, you can for example affect tax amounts derived from the system, in the same way as tax information is changed on the split window of the interface transaction.
CPD_ITEMS LIKE BAPI_CJ_CPD_ITEMS X One-time data
Long text:
In the CPD_ITEMS table, you can assign information for one-time customers or vendors that are contained in line items of the ITEMS table. Basically, the table fields correspond to the fields of the TCJ_CPD table, which are ready for input on the one-time window.
WTAX_ITEMS LIKE BAPI_CJ_WTAX_ITEMS X Withholding tax in the
cash journal document
Long text:
In the WTAX_ITEMS table, you can assign information on the extended withholding tax for a vendor that is contained in a line item of the CJ_ITEMS table. Basically, the table fields correspond to the fields of the TCJ_WTAX_ITEMS table, which can be changed the withholding tax window.
EXTENSION_IN LIKE BAPIPAREX X Container for
'Customer Exit'
Long text:
In the EXTENSION_IN parameter, you can transfer parameters that can be processed further in the BADI CJ_DOCUMENT, which the user of the BAPI BAPI_CASH_JOURNAL_CREATE has to implement.
For example, you can assign data to the TCJ_POSITIONS table in the form of Include CI_COBL or information profitability segments or real estate.
RETURN LIKE BAPIRET2 Return parameter
Long text:
In Table RETURN, the messages of the program are returned to the initiator of the BAPI.
d) Save and activate the changes.
1. Using Transaction SE11, create data type (structure) BAPI_CJ_HEADER in Package CAJO with the short description 'Cash journal document header for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field Data element
COMP_CODE BUKRS
CAJO_NUMBER CJNR
CURRENCY WAERS
CURRENCY_ISO WAERS_ISO
DOC_DATE BLDAT
PSTNG_DATE BUDAT
REF_DOC_NO XBLNR1
BP_NAME CJBPNAME
ALLOC_NMBR DZUONR
TEXT1 CJDOCTEXT100
TEXT2 CJDOCTEXT30
CHECK_NUMBER SCKNR_EB
CHECK_ISSUER CJCHECKISSUER
BANK_KEY BANKK
BANK_ACCT BANKN
BANK_CTRY BANKS
BANK_CTRY BANKS
BANK_CTRY_ISO BANKS_ISO
SCBANK_IND LZBKZ
SUPCOUNTRY LANDL
SUPCOUNTRY_ISO LANDL_ISO
c) Save and activate the changes.
2. In Transaction SE11, create data type (structure) BAPI_CJ_ITEMS in Package CAJO with the short description 'Cash journal line item for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as enhancement category.
b) Create the following fields:
Field Data element
POSITION_NUMBER CJBUZEI
TRANSACT_NUMBER CJTRANSNUMB
P_RECEIPTS BAPIWRBTR
P_PAYMENTS BAPIWRBTR
P_NET_AMOUNT BAPIWRBTR
H_NET_PAYMENT_WT BAPIWRBTR
GL_ACCOUNT HKONT
TAX_CODE MWSKZ
TAXJURCODE TXJCD
VENDOR_NO LIFNR
CUSTOMER KUNNR
POSITION_TEXT CJPOSTEXT
BUS_AREA GSBER
TR_PART_BA PARGB
TRADE_ID RASSC
CS_TRANS_T RMVCT
FUNC_AREA FKBER
CO_AREA KOKRS
COSTCENTER KOSTL
ACTTYPE LSTAR
ORDERID AUFNR
ORDER_ITNO CO_POSNR
CALC_MOTIVE BEMOT
COSTOBJECT KSTRG
CO_BUSPROC CO_PRZNR
PROFIT_CTR PRCTR
PART_PRCTR PPRCTR
WBS_ELEM PS_POSID
NETWORK NPLNR
ACTIVITY VORNR
ASSETMAINO BF_ANLN1
ASSETSUBNO BF_ANLN2
VALUEDATE BF_BZDAT
ASSETTRTYP BF_ANBWA
PLANT WERKS_D
VAL_TYPE BWTAR_D
MATERIAL MATNR
SALES_ORD KDAUF
SCHED_LINE KDEIN
S_ORD_ITEM KDPOS
FM_AREA FIKRS
FUNDS_CTR FISTL
CMMT_ITEM FIPOS
FUND BP_GEBER
FUNDS_RES KBLNR_FI
RES_ITEM KBLPOS
PERSON_NO PERNR_D
BUPLA BUPLA
SECCO SECCO
c) Save and activate the changes.
3. In Transaction SE11, create the data type (structure) BAPI_CJ_TAX_ITEMS in Package CAJO with the short description 'One-time data of cash journal line items for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field Data element
TAX_CODE MWSKZ
AMT_TAX BAPITXBTR
AMT_BASE BAPIFWBAS
TAXJURCODE TXJCD
c) Save and activate the changes.
4. In Transaction SE11, create the data type (structure) BAPI_CJ_CPD_ITEMS in Package CAJO with the short description 'One-time data of cash journal line items for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category
b) Create the following fields:
Field Data element
POSITION_NUMBER CJBUZEI
ANRED ANRED
NAME NAME1_GP
NAME_2 NAME2_GP
NAME_3 NAME3_GP
NAME_4 NAME4_GP
SOLE_PROP STKZN
REP_NAME REPRES
STREET STRAS_GP
POSTL_CODE PSTLZ
CITY ORT01_GP
COUNTRY LAND1_GP
COUNTRY_ISO LAND1_ISO
PO_BOX PFACH
POBX_PCD PSTL2
REGION REGIO
POBK_CURAC PSKTO
BANK_ACCT BANKN
BANK_NO BANKL
BANK_CTRY BANKS
BANK_CTRY_ISO BANKS_ISO
CTRL_KEY BKONT
BANK_REF BKREF
INSTR_KEY DTAWS
DME_IND DTAMS
TAX_NO_1 STCD1
TAX_NO_2 STCD2
TAX_NO_3 STCD3
TAX_NO_4 STCD4
SLS_PUR_TX STKZU
FITYP J_1AFITP_D
TAX_NO_TY J_1ATOID
EQUAL_TAX STKZA
SPRAS CHAR_LG_01
LANGU_ISO LAISO
BUS_TYPE GESTYP
IND_TYPE INDTYP
c) Save and activate your changes.
5. In Transaction SE11, create the data type (structure) BAPI_CJ_WTAX_ITEMS in Package CAJO with the short description 'Withholding tax in cash journal document for transfer to a BAPI'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field Data element
POSITION_NUMBER CJBUZEI
VENDOR_NO LIFNR
WTAXTYPE WITHT
WT_WITHCD WT_WITHCD
W_TAX_BASE BAPIQSSHB
WI_TAX_AMT BAPIQBSHB
c) Save and activate the changes.
6. In Transaction SE11, create the data type (structure) BAPI_CJ_KEY in Package CAJO with the short description 'Key fields for cash journal documents'.
a) Via the 'Extras' menu option, select 'Cannot Be Enhanced' as the enhancement category.
b) Create the following fields:
Field Data element
FISC_YEAR GJAHR
POSTING_NUMBER CJBELNR
c) Save and activate the changes.
7. Using Transaction SE91, create the following messages for message class FCJ and select the 'Self-explanatory' field for each one:
a) 011: 'Document & & & was saved successfully.'
b) 012: 'Enter a gross amount.'
c) 013: 'Enter only the disbursement or incoming payment amount for each document.
d) 014: 'Enter the item numbers for all items or for none of them.'
e) 015: 'The number of tax items may not be larger than the number of items.'
f) 016: 'Only one tax item allowed per tax code/jurisdiction code.'
g) 017: 'Enter the item number for one-time items.'
h) 018: 'With several line items (split), do not enter any withholding tax items.'
i) 019: 'Business transaction without G/L account or tax code.'
j) 020: 'No line item with tax code/jurisdiction code of the tax item.'
k) 021: 'In company code & taxes without jurisdiction code.'
l) 022: 'Do not enter any tax item for posting indicator '3' (T007B-STBKZ)'
m) 023: 'Document could not be saved. Correct the errors listed'
n) 024: 'Business place + section code only with extended withholding tax.
o) 025: 'Net/tax base is deleted for several items or tax items'
p) 026: 'No line item corresponds to one-time item &.'
q) 027: 'Do not enter any withholding tax info if customer not w.tax-relevant'
r) 028: 'Do not enter any withholding tax info if vendor not w.tax-relevant'
s) 029: 'Do not enter any withholding tax info for G/L account posting.'
t) 030: 'Vendor in withholding tax information is not in line item.'
u) 031: 'Only one one-time item is allowed per item number.'
v) 032: 'Only one withholding tax item is allowed per withholding tax type.'
w) 033: 'Number of assigned withholding tax items deviates from master data.'
x) 034: 'No vendor required for business transaction.
y) 035: 'No customer required for business transaction.'
z) 036: 'Enter only receipts for checks.'
8. In Transaction SE37, call the FCJ_SAVE and FCJ_SAVE_DOCUMENT function modules in change mode.
a) Add import parameter I_XBAPI of TYPE BOOLEAN to these function modules. Select the Optional and Pass Value fields and enter the short text 'Indicator whether the call occurs from a BAPI'.
b) Also add the import parameters I_POSTING_NUMBER, LIKE, ISCJ_POSTINGS-POSTING_NUMBER for the function module FCJ_SAVE_DOCUMENT. Select the Optional and Pass Value fields.
c) Save and activate the changes.
9. In Transaction SE37, create the function module FCJ_SAVE_DOCUMENT_BALANCE_BAPI in the function group SAPLFCJ_PROCESS_MANAGER in Package CAJO with the short text 'Save cash journal document and balances for BAPI' as an update module with 'Start immed'.
a) Enter the following import parameters:
Parameter Name Type Associated Type Opt Pass Value
I_COMP_CODE LIKE TCJ_C_JOURNALS-COMP_CODE X
I_CAJO_NUMBER LIKE TCJ_C_JOURNALS-CAJO_NUMBER X
I_CURRENCY LIKE TCJ_DOCUMENTS-CURRENCY X
I_TYP TYPE CJTRANSTYP X
I_DISPLAY_PERIOD_LO LIKE SY-DATUM X
I_DISPLAY_PERIOD_HI LIKE SY-DATUM X
I_POSTING LIKE ISCJ_POSTINGS X
I_POSTING_NUMBER LIKE ISCJ_POSTINGS-POSTING_NUMBER X
b) Enter the following tables:
Parameter Name Type Associated Type
ITCJ_POSTINGS LIKE ISCJ_POSTINGS
ITCJ_WTAX_ITEMS LIKE TCJ_WTAX_ITEMS
ITCJ_SPLIT_POSTINGS LIKE ISCJ_POSTINGS
ITCJ_CPD LIKE TCJ_CPD
10. In Transaction SE18, define the BADI CJ_DOCUMENT. The corresponding interface is IF_EX_CJ_DOCUMENT.
The method has the following 'Changing' parameter: Parameter Type Associated Type
C_ITCJ_SPLIT_POSTINGS Type ISCJ_POSTINGS
C_ITCJ_SPLIT_TAXES Type ISCJ_POSTINGS
C_ITCJ_CPD Type TCJ_CPD
C_ITCJ_WTAX_ITEMS Type TCJ_WTAX_ITEMS
C_EXTENSION2 Type BAPIPAREX
C_RETURN Type BAPIRET2
You can use an implementation of this BADI to change the cash journal structures before the data check is processed.
1. Implement the attached corrections in your system.
2. In Transaction SE37, release the function module BAPI_CASHJORUNAL_DOC_CREATE via the menu path 'Function module' -> 'Release' -> 'Release'.
3. In Transaction SWO1, create the object type BUS2023.
a) Create the following key fields for the object type:
Key field Name Data type reference
CompanyCode Company Code TCJ_DOCUMENTS
-COMP_CODE
CashJournalNumber Cash Journal Number TCJ_DOCUMENTS
-CAJO_NUMBER
FiscalYear Fiscal Year TCJ_DOCUMENTS
-FISC_YEAR
CashJournalDocNo Cash Journal TCJ_DOCUMENTS
Document Number -POSTING_NUMBER
b) Create the 'Create' method synchronously and instance-independent as an 'API function' with the name BAPI_CASHJOURNALDOC_CREATE.
Create the following parameters for the method: Parameter Obj Type Imp. Man. Exp.
Header BUS2023 X X
Testrun BUS2023 X
CompanyCode BUS2023 X
CashJournalNumber BUS2023 X
FiscalYear BUS2023 X
CashJournalDocNo BUS2023 X
Items BUS2023 X X
TaxItems BUS2023 X
CPDItems BUS2023 X
WTaxItems BUS2023 X
ExtensionIn BUS2023 X
Return BUS2023 X
a) Create the 'ExistenceCheck' method synchronously and define the following source code:
begin_method existencecheck changing container.
DATA: l_mandt TYPE sy-mandt.
SELECT SINGLE mandt INTO l_mandt
FROM tcj_documents
WHERE comp_code = object-key-companycode
AND cajo_number = object-key-cashjournalnumber
AND fisc_year = space
AND posting_number = object-key-cashjournaldocno.
check sy-subrc <> 0.
exit_object_not_found.
end_method.
a) Under the menu option 'Goto' -> 'Documentation', define the following text for object type BUS2023:
A cash journal document is assigned to a cash journal and a company code.
It contains a unique document number from a company code-dependent number range interval that is independent of the number range interval of the G/L document. Cash journal documents are also numbered sequentially per company code and cash journal.
A cash journal document contains the offsetting entries for the G/L account of the cash journal in which G/L or person accounts are posted to for the business transaction.
You can save, delete, post or reverse a cash journal document. In the two last cases, there is a corresponding G/L document. This can be a receipt, a disbursement of cash, or the receipt of checks.
1. In Transaction BDBG, set up the IDOC processing for the object type BUS2023 and the method CREATE.
The function module for ALE outbound processing with data refining is ALE_CASHJOURNALDOC_CREATE.
The function module for ALE inbound processing is called IDOC_INPUT_CAJODOC_CREATE.
1. In Transaction 'SALE', maintain the ALE distribution. Here, maintain the steps generally required for a distribution process. Take into account the existing documentation of the operation. Execute the following steps for the BAPI used to save cash journal documents.
a) Maintain the distribution model under the path 'Model and Implement Business Processes' -> 'Maintain Distribution Model and Distribute Views'. The object name is 'CashJournalDoc' and the method name is 'Create'.
b) Execute the menu option 'Edit' -> 'Model view' -> 'Distribute' for the selected model view.
c) Select the path 'Model and Implement Business Processes' -> 'Partner Profiles and Time of Processing' -> 'Generate Partner Profiles'. (See corresponding documentation in document OALE_AUTOPARTN_BD82.) Enter the selected model view in the distribution model and the selected target system as the partner system.
2. To monitor the distribution of the IDOCs, use Transaction BD87 in both the sender system and the receiver system, and you can reach it via the path 'Tools' -> 'ALE' -> 'ALE Administration' -> 'Monitor' -> 'Status Monitor'. The relevant message type is CASHJOURNALDOC_CREATE.
Similar Messages
-
Joint Venture Accounting Posting Period
What is the T-Code for opening Joint Venture Accounting Posting Period ?
The system prompts a warning when posting an operated or non-operated cash calls
I am new to SDN ,can anyone kindly refer to me the link where i can ask questions related to Joint Venture Accounting or Production Sharing Accounting.I have a problem with periods of JVA, although they are closed you can record FI documents,
release 6.
Best regards
Antonella -
Commit Function Module for External System ?
Hi Gurus,
I am using RFC - RFC_UPDATE_TAXES_DOC to post documents into External System.
After I post those documents how to execute Commit fucntion in the external system.
My Try:
Will I be able to commit using BAPI_TRANSACTION_COMMIT -
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' DESTINATION gc_external_system.
Many Thanks,
MadanYes.
It should work, b'coz BAPI_TRANSACTION_COMMIT is itself a RFC func module.
Regards,
Subramnaian -
Not able to post journal voucher because of unbalanced system currency
Hi
I am not able to post journal voucher because of unbalanced system currency (the local currency is matching).
what should be done, i have posted close to 70 entries!!!!!
I am using SAP 2005B patch level 44
please help
ThanksHi santosh,
To the account to which you are posting the entry.What currency you have set for it.
regards,
PankajK -
Payroll posting to External system
Hi,
We are on ECC 6.0 and will be implementing SAP HR. Finance is on an external system and the requirement is to create the payroll posting file from SAP ECC 6.0.
Can anyone tell me some directions on how to configure the system to create a posting file that can be sent to external system? Also, if anyone has a cookook that will be a great help.
Thanks
SalimThis might help:
1) Create segment (WE31)
2) Create IDOC Types (WE30)
3) Create message type (WE81)
4) Link message type with basic type (WE82)
5) Create FM
In the FM all the attributes should be the same for Inbound or Outbound. Basically you can get an example from the std FM eg: Inbound - IDOC_INPUT_DELVRY
Outbound - IDOC_OUTPUT_SHPMNT.
6) Create Process Code (Inbound - WE41/ Outbound - WE42)
IMPORTANT: Before you key in the FM, you are required to add the FM in this table V_TBD51.
7) Link FM with Basic Type
For testing go to WE19.
Here are some of the std program that you can use for IDOC:
1) RSNAST00 - Issuing Output type
2) RBDINPUT - Processing Inbound idocs
3) RBDAPP01 - Processing Idocs that already processed before
4) RBDSEMAT- Stand alone program to generate IDocs (Send Material)
5) RBDMIDOC - Outbound triggered from change pointer
6) RSEINB00 - Convert file to IDOC in status 64 -
External System Handling Units to SAP ECC System and Pack Outbound DO
Hi Guru
Packing Is done in External System for SAP ECC Sales Order Before Outbound Delivery Creation.
How to capture External System Handling Units in to SAP ECC System and Pack Outbound Delivery Line Items.
Please help
Thanks In Advance
SRBit of a cart-before-the-horse situation here.
Lets assume that your business process goes ahead and creates a delivery note, but leaves it unpicked and unpacked. Picking and packing will occur with the inbound IDoc from your external system.
Map the external system data into a basic IDoc type DELVRY0X. I think the current one is DELVRY07.
Use an inbound IDoc message type SHPCON to carry the external system data into your ECC system.
The process code DELV works well with DELVRY0X inbounds. It has lots of user exits. You will need them because you will need a determination process to know which delivery note to update with the external system data.
When you map the handling unit data correctly into the IDoc, the process code will create the handling units on your delivery. The external handling unit numbers should end up in VEKP- EXIDV.
Regards,
zKen -
Use Purchase Accounts Posting System
hi experts,
Can anyone please explain to me what is Use Purchase Accounts Posting System for in SAP Business One?Check this link for Purchase Accounts Posting System.
Re: purchase a/c system in B1 -
Purchase Accounts Posting System
Dear All,
I am using SAP B 1 2007B PL 12
Can anyone tell what is the significane or use of " Purchase Accounts Posting System" option in Basic initialization.
From help i was able to understand
"In localizations where purchase accounting is used, selecting this option enables purchase accounting"
Can anyone guide with help of example so that it will be more clear.
swapnilHi Ashish,
I would like to ask you about the MIRO part of the Purchasing Account Management.
I have configured the following steps in SPRO
SPRO > MM > Val & Acc *** > Acc Determ > Acc Determ w/o Wizard > Pur Acc mgmt
1) Activate Account in Co Code
2) Calculation of Value for Purchase Account
3) Separate account document for Pur Acc Posting
a) Activate Sep Acc Doc for Pur Acc Post in Valuation Area
b) Create new document type for separate document
c) Configure Number Range for New Doc Type
d) IM: Configure doc type for separate FI doc
(I´ve copied WE doc and name it as WZ)
e) IV: Configure doc type for separate FI doc
(I´ve copied RE doc and name it as RZ)
Also configured OBYC: EIN, EKG, FRE
During Good Receipt, i succesfully get the separate accounting with accounts
(D) Purchase Account
(C) Purchase Offseting Account
However, when i want to get the same during Invoice Verification i only get the regular Accounts:
(D) Vendor Acc
(C) GR/IR offseting account
As far as I understand as per SAP documentation, i should be able to have this Purchasing Account Management in both operations (G.R. and I.Verification).
Could you explain how to configure this part?
many thanks in advance for any information or comment.
Regards,
Nicolas. -
Account posting keys involves for process of third party order
hi
pls tell me the process of third party order and whos account stock will be debited and tell me the account posting keys involves in this process and how it operates
regards
Ram
Edited by: Ian Wong on Aug 13, 2008 7:06 PMTHIRD PARTY SCENARIO
In third-party order processing, your company does not deliver the items requested by a customer. Instead, you pass the order along to a third-party vendor who then ships the goods directly to the customer and bills you. A sales order may consist partly or wholly of third-party items. Occasionally, you may need to let a vendor deliver items you would normally deliver yourself.
Process Flow
The processing of third-party orders is controlled via material types. Material types define whether a material is produced only internally, can be ordered only from third-party vendors, or whether both are possible. For example, a material that is defined as a trading good can only be ordered from a third-party vendor. However, if you manufacture your own finished products, you may also want, from time to time, to be able to order the same type of product from other vendors.
Processing Third-Party Orders in Sales
Third-party items can be created automatically by the system, depending on how your system is set. However, you can also change a standard item to a third-party item during sales processing manually.
Automatic third-party order processing
If a material is always delivered from one or more third-party vendors, you can specify in the material master that the material is a third-party item. During subsequent sales order processing, the system automatically determines the appropriate item category for a third-party item: TAS. To specify a material as a third-party item, enter BANS in the Item category group field in the Sales 2 screen of the material master record.
Manual third-party order processing
In the case of a material that you normally deliver yourself but occasionally need to order from a third-party vendor, you can overwrite the item category during sales order processing. For a material that you normally deliver yourself, you specify the item category group NORM in the material master.
If, as an exception, you use a third-party material, change the entry TAN to TAS in the ItCa field when processing the sales document. The item is then processed as third-party item.
If address data for the ship-to party is changed in the sales order in third-party business transactions, the changed data will automatically be passed on to purchase requisition and also to the purchase order ,if one already exists. In the purchase order, you can display the address data for the ship-to party in the attributes for the item.
You can only change the address data for the ship-to party in the sales order for third-party business transactions, and not in the purchase order.
Processing Third-Party Orders in Purchasing
When you save a sales order that contains one or more third-party items, the system automatically creates a purchase requisition in Purchasing. Each third-party item in a sales order automatically generates a corresponding purchase requisition item. During creation of the requisition, the system automatically determines a vendor for each requisition item. If a sales order item has more than one schedule line, the system creates a purchase requisition item for each schedule line.
Purchase orders are created from purchase requisitions in the usual way. For more information about creating purchase orders, see the Purchasing documentation. During creation of the purchase order, the system automatically copies the delivery address of your customer from the corresponding sales order. In a sales order, you can enter purchase order texts for each third-party item. When you create the corresponding purchase order, the texts are automatically copied into the purchase order. The number of the purchase order appears in the document flow information of the sales order.
All changes made in the purchase order are automatically made in the sales order as well. For example, if the vendor confirms quantities and delivery dates different from those you request and enters them in the purchase order, the revised data is automatically copied into the sales order
You process third-party items by creating a normal sales order. In overview for the order, you can then overwrite the default item category (TAN in the standard system) with the special item category for third-party items: TAS
Billing Third-Party Orders
If relevance for billing indicator for the item category has been set to B (relevant for order-related billing on the basis of the order quantity) in Customizing, the system includes the order in the billing due list immediately. If, however, the indicator has been set to F (relevant to order-related billing on the basis of the invoice quantity), the system does not include the order in the billing due list until an invoice from the vendor has been received and processed by the purchasing department. In the standard system, item category TAS (third-party order processing) has been given billing-relevance indicator F.
In the first case, the third-party order is considered to be completely billed only when the invoiced quantity equals the order quantity of the sales order item. In the second case, each time a vendor invoice is received, a customer invoice is created for the quantity in the vendor invoice and the order is considered to be fully invoiced until the next vendor invoice is received.
If you have activated billing-relevance indicator F for item categories in Customizing, billing can refer to the goods receipt quantity instead of the incoming invoice quantity.
You can control whether the invoice receipt quantity or the quantity of goods received is relevant for billing in Customizing for copying control for billing at item level.
FOR YOUR PROCESS Individual Purchase Orders WELL GIVE THE RIGHT SOLUTION
Individual purchase orders are used when your customer orders goods from you that are not in stock and must be ordered from one or more external vendors.
Process Flow
During sales order entry, the system automatically creates a purchase requisition item. The purchasing department creates a purchase order based on the requisition and the vendor ships the goods directly to you (unlike third party order processing, where the vendor ships directly to your customer). You then ship the goods to your customer. While the goods are part of your inventory, you manage them as part of the sales order stock. Sales order stock consists of stock that is assigned to specific sales orders and cannot be used for other purposes.
Goods receipt will be posted when ever the vendor ships the goods to our customer.
We will do this transaction in SAP using MIGO.
Invoice receipt is done when the Vendor sends us the invoice.. ( I.e Billing ).
It can be done using MIRO.
THe above two steps are standard and manual. There are many other ways that the actual process can happen. If the client follows EDI standards then the Goods receipt and Invoice receipt can be done through IDOCs automatically.
Process Flow for 3rd Party Sales
Customize the third party sales in summary:
Prerequisites for 3rd party sales,
Purchasing org,
purchasing group,
assign the Purchase org to company code
assign Purchase org to plant,
should not maintain the stock in material, it should be trading goods,
1. Create Vendor XK01
2. Create Material Material Type as "Trading Goods". Item category group as "BANS".
3. Assign Item Category TAS to Order type that you are going to use.
4. A sale order is created and when saved a PR is generated at the background
5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor.
6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO
7. Goods receipt MIGO
8. Goods issue
9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the config and, therefore, there is no delivery process attached in the whole process of Third party sales.
10. Billing *--
SD - 3rd party sales order Create Sales Order
VA01
Order Type
Sales org, distr chnl, div
Enter
Sold to
PO #
Material
Quantity
Enter
Save
SD - 3rd party sales order View the PR that is created with a third party sales order
VA01
Order Number
Goto Item Overview
Item ->Schedule Item
SD - 3rd party sales order View the PR that is created
ME52N
Key in the PR number
Save
SD - 3rd party sales order Assign the PR to the vendor and create PO
ME57
Key in the PR number
Toggle the "Assigned Purchase Requisition"
Execute
Check the box next to the material
Assign Automatically button
Click on "Assignments" button
Click on "Process assignment"
The "Process Assignment Create PO" box , enter
Drag the PR and drop in the shopping basket
Save
SD - 3rd party sales order Receive Goods
MIGO_GR
PO Number
DN Number
Batch tab , click on classification
Serial Numbers tab
Date of Production
Flag Item OK
Check, just in case
Post
Save
SD - 3rd party sales order Create Invoice
MIRO
Invoice Date
Look for the PO , state the vendor and the Material
Check the box
Click on "Copy"
Purchase Order Number (bottom half of the screen)
Amount
State the baseline date
Simulate & Post
Invoice Number
*Invoice blocked due to date variance
SD - 3rd party sales order Create a delivery order
VL01N
In the order screen , go to the menu Sales Document , select "Deliver"
Go to "picking" tab
State the qty and save
SD - 3rd party sales order Create a billing document
VF01
Ensure that the delivery document is correct in the
Enter
Go to edit -> Log
Save
Third party order processing is as follows:
Assume three companies X, Y and Z
X - The company,
y - The customer
Z - Vendor
When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
If he is procuring the goods, there are two methods that are generally followed:
Method 1) After receiving the PO from Y, X creates a sales order against Y.
Now at the same time he also creates a PO to a vendor Z to produce the goods
Z produces the goods and supplies to X
X receives the goods from Z
Then X delivers the same goods to Y.
After that X invoices Y and Z invoices X.
Note : Here there is no direct/ Indirect relation between Z and Y.
This process is known as Trading Process. and the Material here is created with Material type HAWA.
The other method is a Third party order processing method:
Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
Now Z supplies the material to Y and acknowledges the same to X.
Z will send a copy of delivery acknowledgement and invoice to X.
After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
The next step for X is to create an invoice and submit to Y
Only after the invoice verification document is posted then only X can create an invoice for Y.
This is the business flow that is followed for third party order configuration.
There are few steps that have to be configured to enable the system to function as mentioned above.
Step1)
If you are always following a third party process for a material then you have to create the material using item category group BANS.
The procurement type should be marked as External procurement (F) in MRP 2 view of the material master record.
if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurement ( in house manufacturing and external procurement).
Step 2)
the item category in the order should be manually changed as TAS.
For that you need to configure the item category determination
Order type + item cat Group + Usage + High level = Item cat + Manual item cat
OR + NORM + + = TAN + TAS
OR + BANS + + = TAS
Step 3)
make sure that during the item category configuration for TAS you need to mark relevant for billing indicator as F
step 4)
The schedule line category for this type should be CS.
make sure that you mark subsequent type as NB - purchase requisition in this schedule line category as this will trigger the purchase requisition order immediately after the creation of the sales order and the PO to vendor is created against this purchase requisition.
Award if Helpful,
Regards
Priyanka.P -
Error when creating Final Accounting Post to GL in AR
Hello,
I currently getting an error while creating Final Accounting Post to GL
I have changed the Profile Option SLA: Enable Trace to <null> as mentioned in the solution on metalink. But still I'm getting this error.
If anyone has encountered the error(LOG) below; please reply me as soon as possible
thanks
mevin
THE LOG
Subledger Accounting: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XLAACCPB module: Create Accounting
Current system time is 14-AUG-2009 09:36:54
XDO Data Engine Version No: 5.6.3
Resp: 50832
Org ID : 102
Request ID: 499751
All Parameters: P_APPLICATION_ID=222:P_SOURCE_APPLICATION_ID=:P_DUMMY=:P_LEDGER_ID=2089:P_PROCESS_CATEGORY_CODE=:P_END_DATE=:P_CREATE_ACCOUNTING_FLAG=N:P_DUMMY_PARAM_1=:P_ACCOUNTING_MODE=:P_DUMMY_PARAM_2=:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D:P_TRANSFER_TO_GL_FLAG=Y:P_DUMMY_PARAM_3=:P_POST_IN_GL_FLAG=Y:P_GL_BATCH_NAME=:P_MIN_PRECISION=2:P_INCLUDE_ZERO_AMOUNT_LINES=:P_REQUEST_ID=:P_ENTITY_ID=118514:P_SOURCE_APPLICATION_NAME=:P_APPLICATION_NAME=:P_LEDGER_NAME=:P_PROCESS_CATEGORY_NAME=:P_CREATE_ACCOUNTING=:P_ACCOUNTING_MODE_NAME=:P_ERRORS_ONLY=:P_ACCOUNTING_REPORT_LEVEL=:P_TRANSFER_TO_GL=:P_POST_IN_GL=:P_INCLUDE_ZERO_AMT_LINES=:P_VALUATION_METHOD_CODE=:P_SECURITY_INT_1=:P_SECURITY_INT_2=:P_SECURITY_INT_3=:P_SECURITY_CHAR_1=:P_SECURITY_CHAR_2=:P_SECURITY_CHAR_3=:P_CONC_REQUEST_ID=:P_INCLUDE_USER_TRX_ID_FLAG=:P_INCLUDE_USER_TRX_IDENTIFIERS=:P_USER_ID=:DebugFlag=
Data Template Code: XLAACCPB
Data Template Application Short Name: XLA
Debug Flag:
{P_ACCOUNTING_REPORT_LEVEL=, P_DUMMY=, P_ACCOUNTING_MODE_NAME=, P_ERRORS_ONLY_FLAG=N, P_REPORT_STYLE=D, P_GL_BATCH_NAME=, P_END_DATE=, P_SECURITY_INT_3=, P_SECURITY_INT_2=, P_SECURITY_INT_1=, P_VALUATION_METHOD_CODE=, P_POST_IN_GL=, P_TRANSFER_TO_GL=, P_TRANSFER_TO_GL_FLAG=Y, P_INCLUDE_USER_TRX_IDENTIFIERS=, P_USER_ID=, P_PROCESS_CATEGORY_NAME=, P_ERRORS_ONLY=, P_DUMMY_PARAM_3=, P_SECURITY_CHAR_3=, P_DUMMY_PARAM_2=, P_SECURITY_CHAR_2=, P_DUMMY_PARAM_1=, P_SECURITY_CHAR_1=, P_ENTITY_ID=118514, P_PROCESS_CATEGORY_CODE=, P_INCLUDE_ZERO_AMT_LINES=, P_LEDGER_ID=2089, P_POST_IN_GL_FLAG=Y, P_APPLICATION_ID=222, P_INCLUDE_USER_TRX_ID_FLAG=, P_APPLICATION_NAME=, P_REQUEST_ID=, P_CONC_REQUEST_ID=, P_LEDGER_NAME=, P_SOURCE_APPLICATION_ID=, P_CREATE_ACCOUNTING=, P_CREATE_ACCOUNTING_FLAG=N, P_MIN_PRECISION=2, P_SOURCE_APPLICATION_NAME=, P_INCLUDE_ZERO_AMOUNT_LINES=, P_ACCOUNTING_MODE=}
Calling XDO Data Engine...
[081409_093744202][][EXCEPTION] SQLException encounter while executing data trigger....
java.sql.SQLException: ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.accounting_program_document. ORA-01086: savepoint 'SP_EVENTS' never established
ORA-20001: -: XLA-95103: An internal
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 262
ORA-06512: at line 4
at java.lang.Throwable.<init>(Throwable.java:57)
at java.lang.Throwable.<init>(Throwable.java:68)
at java.sql.SQLException.<init>(SQLException.java:55)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:215)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:965)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3445)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4394)
at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:699)
at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:255)
at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:205)
at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:237)
at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:364)
at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:236)
at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:293)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Start of log messages from FND_FILE
14-AUG-2009 09:37:19 - Beginning of the Report
GL Inerface tablename = GL_INTERFACE
GL Inerface tablename = GL_INTERFACE
tablename = GL_INTERFACE
14-AUG-2009 09:37:19- Submitting the Journal Import
GL Inerface tablename = GL_INTERFACE
GL Inerface tablename = GL_INTERFACE
tablename = GL_INTERFACE
14-AUG-2009 09:37:19- Submitting the Journal Import
14-AUG-2009 09:37:44- Journal Import completed
ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.accounting_program_document. ORA-01086: savepoint 'SP_EVENTS' never established
ORA-20001: -: XLA-95103: An internal
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 262
ORA-06512: at line 4
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
Current system time is 14-AUG-2009 09:37:45
---------------------------------------------------------------------------select * from gl_je_sources_tl;
main columns to look at are:
IMPORT_USING_KEY_FLAG
je_source_name
je_source_key
user_je_source_name
select * from gl_je_categories;
main columns to look at are:
je_category_key
user_je_category_name
If import_using_key_flag is Y for your je_source (Receivables), for the application (222) you are running Create Accounting in Final Post Mode, then apply the patch 8568620
By
Vamsi -
IDOC's to external system in different queues.
Our external system( non sap ) can accept IDOC's HRMD_A, I wanted to know is there a way I can send
1.)Create
2.)Change
3.) Delete
in three different queues from my SAP system. I have setup the distribution model where i have defined the sender and receiver and message type but I wanted to know is there a way if this can be achieved.
Points will be awarded.
AnkurHi ankur,
u can send the idoc to non-sap system
when u execute an outbound process an ALE or EDI is processed
using ALE u can send the idoc to non-sap system also
Continued data exchange after a release upgrade without requiring special maintenance
regards,
sindhu -
Configure plain http adapter for receiving message from an external system
Hi,
we use Pi/700.
Now I have an external system and I have to use HTTP (plain) to send messages to XI (via plain http adapter).
I have no experiences with HTTP!
In the external system I can only configure "URL, Username, Password" for sending messages - that's all!
What do I have to configure in XI (communication channel, abap-stack, java-stack,...)?
I don't know the URL of my XI-system. Is there an transaction code to get this information?
Why do I need a Username/Pasword?
For testing I can use a "http-post test tool" I found here in this forum.
Thank you all for any help!
Regards
WolfgangHi Hummel,
In Exteranl System u have to use these values
name="myhost" value="xiserver"
name="myport" value="8000"
name="mysystem" value="XY_BSservice"
name="myinterface" value="Order_out"
name="mynamespace" value="urn:xi:hcl:powebapp"
name="myqos" value="BE"
name="myclient" value="300"
name="myuser" value="XYZCLNT"
name="mypass" value="xiuser"
Here My system is the Business service created in Integration directory of XI, Interface is the one created in Integration Repository (This is Outbaound from external sys to XI)
In XI U have to create
Data Types : 1) Source Structure data type(from extenal sys)
2) Target structure (where u want to send from XI)
Message Types : 2 with above DT's
Message Interface: 1) Outbound, Async (Order_out)
2) Inbound , Async (for the target sys)
Then Message mapping and Interface mapping as usual..
And in ID u have to create 2 services one is XY_BSservice for sending system and the other is for receiving system...
For sending system no communication channel required...
Hope u will get idea from the above..
Need any further u r welcome..
Regards
Sridhar -
FSCM 9.0: COBOL Process GLPPPOST does not post Journal Entry correctly
Folks,
Hello. I am workin on FSCM 9.0 General Ledger module. "Edit Journal" is AE program that works correctly. But "Post Journal" is a COBOL program that does not works correctly.
COBOL process GLPPPOST posts only debit accounts of a Journal entry into table PS_LEDGER but does not post credit accounts of a Journal Entry into table PS_LEDGER. When run the Ledger Report, the report has only column headers and has no data.
Does FSCM 9.0 have a problem or COBOL process does not work correctly ? Can any folks help me ? Thanks.Folks,
Hello. Thanks a lot for replying.
I linked my Ledger Group RECORDING with my Business Unit BU01 using "Set Up Financials/Supply Chain > Business Unit Related > Ledgers For A Unit". Then linked UserID VP1 with BU01 in User Preference. I have checked all information about the 3 concepts (VP1, BU01 and RECORDING) and don't see anything wrong.
I suspect the problem is in the Journal Line page because its Chartfileds belong to 2 SetID (SHARE and FEDRL) and 2 Business Unit (BU01 and BU02).
When define Chartfields value using "Setup FSC > Common Definition > Design Chartfield > Define Value", I see Chartfields "Fund", "Class" and "Program" with SetID "FEDRL", and other Chartfields with SetID "SHARE". The 2 SetIDs are default in the system.
Because one Business Unit (BU01) can link to only one SetID (SHARE), I create one more Business Unit BU02 and linked with SetID "FEDRL". Thus, when create a Journal entry using "General Ledger > Journal > Create Journal ", we type in Business Unit (BU01) and Ledger Group (RECORDING) in Header page, but in Line page, some of Chartfields link with SetID SHARE and BU01, and some of Chartfields link with SetID FEDRL and BU02. The journal entry indicates "Inter/Intra Unit Journal". When select "Edit Journal" and click "Process", the message comes up as follows:
"Ledger Group RECORDING is not valid for Business Unit BU01. Ledger Group defined for this journal is not valid for the Business Unit BU01".
My question is: That the Chartfields in Journal Line page link with 2 SetIDs and 2 Business Units causes the above error ? Can any folks help ? Thanks. -
Sending payroll from external system to SAP
Hello SAP experts,
please could you help me to find optimal solution for the following scenario?
We use external system which generates payroll and we need to send the data to SAP. SAP then should post it to a bank and also to GL accounts.
We can not use SAP Payroll because it will not be implemented.
Please could you find me answers to following questions:
1. To what SAP module we should send the payroll?
2. What data we should transfer to SAP?
3. What kind of settings SAP requires (customization, master data)?
Thank you very much for your help and have a nice day
Michal1. customizing :
a ) wage type customizing : you should create(oh11 tcode /modify(sm31 v_512w_o) wage types , how many different wage type you need, some wage types are in system default.
ie basic pay. overtime
b) hr - fi integration customizing
you should do related customizing steps , with basicly wage type - symbolic account
and symblolic account - gl account customizing
2. you should external payroll results to t558a , t558b, t558c tables,
in deail : http://help.sap.com/saphelp_4.70/helpdata/en/5a/f57415558f4e52925b05aa57dad09d/content.htm
3. after then you can run fi posting for payroll, se38 rpcipe00 program, tcode may be different in your country grouping,
you can ask question, if you want in detail. -
Which idoc type allows to send plant/sloc info to external system?LOISM001?
Dear EDI Experts,
we are looking for a solution for the following issue:
An external system (Mobile solution) shall get plant/stock info from SAP ERP.
Process:
1.Plant/Slocation is NOT empty, e.g. Material 1100 -> 100 PC
2. Stock is posted to Pant/Sloc, e.g. Material 1110 -> 50 PC + Mat. 1200 -> 80 PC
For the stock movement idocs can be generated BUT we need ALL stock of Plant/Sloc in idoc
-> 100 PC of 1100
-> 50 PC of 1110
-> 80 PC of 1200
As far as I know NO standard IDOC type exists which offers to transfer such info.
I came across the LOISM001 (to be triggered via transaction POIT) idoc which may meet the requirments. BUT it creates an idoc per material.
Questions:
1. LOISM001: Is there any chance to combine all materials of a plant/storage location to ONE idoc?
2. Any other idoc type suitable and how to trigger automatically?
Many thanks
Regards
JW
Edited by: Jens Wolf on Jul 1, 2008 3:34 PMHi !
You may check out the PROACT01.
It's designed to transmit stock data.
Hope that helped a bit.
Rainer
Maybe you are looking for
-
Is there any way to download a backup to icloud over the internet
is there any way to download a backup to icloud over the internet
-
Sales order item ontime delivery status at order level in Cube
Hi Guys, We have a requirement, currently we have sales order item information in cube where we have some thing called OTD status this status is based on actual GI date and requested date so we have 3 staus at each sales order item level ontime, ea
-
Post unplanned delivery cost to different freight G/L Accounts
Hi, Regarding the freight costs the business process is at the time Purchase Order creation, the company does not know what is the freight costs that is going to be charged by the vendor. The freight charges will be known when the vendor sends the I
-
What is the best way of doing it? SAP Gui or HTML gui
What is the best recemended option of SAP Win gui or HTML gui doing it for the Portal for R/3 transactions. I heard there is much network space will take if i use HTML gui for more than 1000 users, when u consider. Ur suggestions are Welcome. Pl expl
-
Layers palette disappears when I click on my project
I looked but can't find a help reference that addresses this problem. The layers palette disappears everytime I click on my project. I want it to stay visible, without having to click F7, or go to Windows...Layers every time! How do I tell it to stay