Vendor Loan

Hi sapers
This is related to vendor receipt
Requirement like this Client receive the money from vendors this not a security it is like a loan after some period may be 6 or 1 year client paid this amount.
With out invoice how to repay the money and receipt also this is not down payment
this not a SPL Gl indicator
How to map this one helpfull answers rewarded.

Hi
First of all, please know how this is treated in the books of accounts of the Client. Ascertain the legality of this transaction.
If you want to treat this as a loan, you can do it by posting the amount to a GL account say, for ex. "Loan from others" or so.
Regards

Similar Messages

Vendor employee

hi,
in want create a Vendor in my vendor master records so that when ever a loan given to employee is recoded to vendor account.
could u ple give me the accounting entries
1-when the loan is given to employee
2-loan reimbursement by the employee
there is a reconciliation account attached to the vendor:
also i want to know how to enter the loan given to the vendor in the sap system?
please reply soon.urgent

Hi,
Loan payment:
F-47 down payment request
F-48 down payment or F110 print check
Open item on the debit side appears of Vendor
Loan repaid by employee i.e., received by company
Option 1
Receive through F-51, clearing the above open item you can receive the payment
Option 2
Receive through F-52. In this case both ope items appear on both sides of the Vendor account. You do F-44 subsequently.
Assign points if helpful.

While uploading data for employee as a vendor (with their loans and advance

Hi,
We are going for one company live. We are not taking HR module as of now.
We are creating employee as a vendor for all employees with outstanding loans and advances.
Now while uploading initial data for these employee (created as vendor), business wants personal loan outstanding balances employee as a vendor wise.
Generally in case of normal vendor, we treat like
Vendor A/C Dr
to takeover creditors a/C Cr
while going for initial upload.
In above case what should we do if we want outstanding balances (personal loan) while initial balance upload?
Thanks,
Taral Patel

Hi,
You can create a separate employee vendor for Advances paid to them with an assignment to a separate recon account titled as Advance to Employees. Later, you can upload the entries by Debiting the Employee Advance Vendor account and crediting Vendor Upload Account.
Advances paid to employees (recon account) will represent in the TB as a separate line item forming an MIS.
Regards
Hari

Mapping of Loan to Vendor Account

Dear Experts,
As per my issue, I have created Vendor Account, mapped it with employee number as well. I have done all the configuration settings. When an employee has single loan, in that case, this works perfectly fine, going to a specific clearing account. My issue is when an employee has multiple loan types, then a cumulative value goes to the clearing account GL. For Eg., in out scenario we have following loan types:
1. Other Loan
2. Marriage Loan
3. Vehicle Loan
As of now cumulative value goes to respective vendor Account. Issue is to bifurcate this to different Loan GL's.
Kindly help me resolve the issue, as this is very urgent.
Regards,
Bhagyashree

Hi Praneeth,
I have created custom wage types for different loan types. Can you explain me in detail, how to map them?
Regards,
Bhagyashree

Posting Loan to Vendor Employee

Dear Experts,
We're in 4.7. We have a requirement where we need to keep track of loan payment of all our individual employees. Is it possible to post the loan payment in payroll individually to each and every corresponding vendor employees ? Any input will surely be appreciated.
Thanks and regards,
Arief

Hi
You can do the following.
1.Define your employees as vendors and attach the employee code to respective vendor.
2.Define Symbolic Accounts
In this step, you create the symbolic accounts that you require for posting to Accounting.
A symbolic account has the following characteristics:
A four-character alphanumberic code
A descriptive text
An account assignment type (AA type). This defines the type of posting (posting to expense account, posting to payables account, and so on) that applies to the wage types that are posted to the symbolic account.
An employee grouping for account determination (EG) indicator
The following table shows what kind of account and what transaction is linked to an account determination type and what additional information (for example, for cost assignment) is also included in the posting transaction.
AA type Meaning Transaction Additional fields
C posting to expense account HRC cost assignment
CN posting to expense account HRC cost assignment
without quantity   without quantity
R posting to expense account HRC
if accounting is installed in
R/2 System.
F posting to bal. sheet account HRF
FL posting to bal.sheet account HRF
for checking balance
in retroactive accounting
(recalculation difference account)
FO posting to bal. sheet account HRF
(original periods for
wage types whose amount
cannot change
retroactively)
Q posting to bal. sheet account HRF personnel number
with personnel number
D posting to personal   HRD acc. determination
customer accounts   with personnel number
DF posting to fixed customer HRD direct assignment
    of customer account
L posting to customer HRD acc. determination
account(for specific loan)   with personnel number
    loan type,
    sequential number
K posting to personal vendor accounts HRK acc. determination with
    personnel number
KF posting to fixed vendor HRK direct assignment
acc.   of vendor account
Note the following with regard to account assignment types:
In the standard system, no quantities are transferred from wage types in the payroll result to the payroll documents and the resulting accounting documents, although information on quantities is available on the report log for report RPCIPE00 (or RPCIPX00). It is also possible to modify the system to access this information. The account assignment type CN is only useful if you have made this modification and if, in certain instances, you want to suppress the transfer of quantity information.
The account assignment types FL und FO are only of use if there are cross-company code transactions. For more information on customizing cross-company code transactions, refer to Posting to Company Code Clearing Accounts.
We recommend that for symbolic accounts with account type FO, you determine the account in Accounting independent of the Employee grouping for account determination (Feature PPMOD). For this reason, only one G/L account is provided for the payment of wages and salaries as standard. If you determine this G/L account depending on the employee grouping for the account determination, this can lead to inconsistencies when posting the retroactive accounting results. This is due to the fact that when posting retroactive accounting results for wage types that cannot change retroactively, a technical posting takes place (for example, for the wage type Payments (/559)). Since this technical posting usually takes place in the same account in Accounting, it balances to zero and does not appear in the posting document. However, if you determine this account independently of the employee grouping for account determination, and an employee falls in a different employee grouping due to a retroactive change in the HR master data or feature PPMOD, the technical posting cannot balance to zero because two accounts are affected in Accounting. This is why you have to make changes manually in this case.
Example
The wage types Basic pay and Overtime both represent personnel costs and should therefore be posted to expense accounts. You also want to assign these wage type amounts to Cost Accounting objects. Both wage types are dealt with in the same way as far as posting is concerned and can therefore be posted to the same symbolic account. You must specify the account assignment type C, since, in Accounting, there should be a posting to expense accounts and Cost Accounting should be provided with information.
Requirements
You have carried out the step Define Employee Grouping for Account Determination
Standard settings
Symbolic accounts are already set up in the standard system. In this step, you can modify these to meet your requirements.
Recommendation
We recommend that you do not change the definition of the symbolic accounts. If changes to the definition of the symbolic accounts are necessary, you should map the changes using new symbolic accounts.
Activities
1. Check that the existing symbolic accounts meet your requirements. Note the EG indicator. If this indicator is set for an account, posting to this account also considers employee grouping for account determination. With the exception of the key (column SymAcc), you can change the default values.
2. To create additional symbolic accounts, choose New entries
3. To delete unnecessary symbolic accounts, mark the account and choose Edit -> Delete.
Further notes
Symbolic accounts are not country-specific.
3.Assign Vendor Accounts
In this step, you make the settings required for posting to vendor accounts.
There are two kinds of vendor accounts available:
Fixed vendor accounts: Employee grouping for account determination offers the most precise means of control for posting to fixed vendor accounts.
Employee vendor accounts: Posting to employee vendor accounts enables posting for a specific personnel number.
In this step, you make entries in table T030 for the assignment of vendor accounts to symbolic accounts.
Example
Fixed vendor account
You want to deduct dues to various unions from the employees in your enterprise. For each union, you have set up a specific wage type for dues and a specific symbolic account. In this step, you assign a fixed vendor account to each of these symbolic accounts.
Employee vendor account
You want to post dues to a different vendor account for each employee. To this effect, you have created a symbolic account for all employees. In this step, you specify how the corresponding employee vendor accounts are determined.
Requirements
You have created the required vendor accounts in Financial Accounting.
You have carried out the step Define Symbolic Accounts. In that step, you created symbolic accounts with the relevant account assignment types (KF for fixed vendor accounts, K for personal vendor accounts). In that same step, you flagged the indicator EG-depend for symbolic accounts to which you want to post in line with the Employee grouping for account determination.
If you want to post to employee vendor accounts, you have entered the relevant personnel number in one of the following fields in the vendor master data of Financial Accounting. We recommend that you use the Personnel number field. If you use another field, you must enter the personnel number with leading zeros.
Personnel number
Search term
Telephone 2
Data line
Teletext number
Standard settings
There are no standard settings for posting to vendor accounts. If, in the step Define Symbolic Accounts, you have not created any symbolic accounts with the account types KF or K, you do not have to carry out the step Assign Vendor Accounts.
Activities
1. Enter the required chart of accounts.
2. To make settings for the posting procedure Personnel posting to vendors (HRK), choose Rules
3. Choose Posting key. Enter the posting key for postings to vendor accounts or copy the default values (21 for debit posting and 31 for credit postings).
4. Choose Accounts. Make the corresponding entries in the table T030.
a) If you want to assign a fixed vendor account to a symbolic account, and if required, an employee grouping, enter the number of the vendor account in the Acco column.
b) If you want to assign an employee vendor account to a symbolic account, and, if required a employee grouping, enter the relevant key (see table below) in the Acco column.
Personnel number in field (Vendor master data) Entry in the Account column (T030)
Personnel number    *0002
Search term    *0001
Telephone 2    *0003
Data line    *0004
Teletext number    *0005
Further notes
It is not possible to use the special G/L indicator with posting to customer accounts.
in summary whatyou do is defne a symbolic account of type K , link your wage type to this sym account , define the posting to vendor with *0002
regards
Pravin

Loan from Vendor Employee

Hi
Our directors are created as Employee Vendor. There are some cases where company take loan from directors. We have created these "loansfrom directors" as as special GL indicators. Now i want to know how to take loan from directors vendors.
I tried using F-48. But there is no posting key option in F-48. I do not want to use F-02 or F-42. Because using these TCodes will be like posting a JV because we need to give posting keys for all line items, etc.
So let me know how can i post these loan (special GL indicators) from vendors.
Please help
Edited by: Meenu_ND on Oct 21, 2011 5:36 PM

Hi
I went to posting key 29 (debit vendor special GL). Then i deleted that special GL indicator from the list in posting key.
I tried posting in F-48. I expected that it will post in posting key 39. But its gave error "The entry 29 S is missing in table TBSLT"
I pressed enter three times and it allowed me to post the entries.
Hence entry posted was:
Vendor A/c.. Dr (posting key 29)
To incoming bank account. (posting key 50)
So now there are two queries:
1. Same query, how to trigger posting key 39 (instead of 29)
2. How it allowed me to post entry even though i deleted that special GL indicator from posting key 29

Loans: Introduce vendor account during loan payments

Hello folks,
I have Loans managment module working fine for a bunch of flows. I would like to substitute a g/l account that we use during payment with a vendor account. Wondering if I could get some inputs on this.
We have receivable loans, not giving.
In the Accout Determination, I've configured a flow Z120 with Payment transaction 1 and a posting key 40 to the balance sheet account(276510) and 50 to a bridge account(275325). When this flow is posted, a payment request is created between the bridge account and the house bank's payment sub-account(175562). That would be a debit on bridge account(275325) and a credit on bank's payment sub-account(175562). So I run F111 and execute the payment. And then when the back statement comes in, an entry between 175562 and 175560 is made.
Now, I would like to replace this bridge account with a vendor. The primary reason is, the client wants to calculate withholding tax on every payment, interest and capital. Wondering what my options are?
In Account Determination, in the accounts section, in the g/l acct field, I don't know how to specify a vendor account against a acct symbol for the account determination to happen. There is only option for g/l account or +++++ for bank g/l accounts.
Should this be configured some place else. Not sure where I'm missing the part where I could use a vendor instead of using a g/l account as a bridge.
Also in SPRO, in the "Company code settings for product types", the FI posting field for my product is of type 4, which is "Actual records in subledger, posting in FI without customer". Should this be changed to 3, which is "Actual records in subledger, FI posting with customer" - wondering if this would open up a relation with a customer/vendor.
Any help greatly appreciated.
Thanks.

Thanks Kumar. Most of the steps got executed successfully.
Step 1:The moment I changed the FI posting from 4 to 3, I received an error in disbursement saying couldn't determine customer. I did not have a customer role in my BP. I set that with recon account and was able to do disbursement. The disbursement screen looks different too, with an added customer field populated and read-only. I think we are good there.
Step 2: I've ignored third party payment, I did revert it to uncheck the way it was.
Step 3: In Account determination, I configured one more posting specification for my Flowtype(Transaction type), payment transaction 'X', posting category 42. posting key 40(debit) for my interest account and 14(credit) for the new 2.4.4 symbol. I gave the BP/client's recon account g/l account against this new account symbol 2.4.4.
Now when I tried to do a post planned record, it wouldn't pick the newly created posting specification X. It still picks the one with payment transaction 1.
The documentation says, X would be picked if (a) posting for product type made via customer account and (b) payment transaction indicator set for the flow/condtion.
Here bullet (a) is true, because I could see the customer number when I do the disbursement. Now with regards to bullet (b), I've set done the following:-
-In flow type, I have the field "Payment request" checked.
-In condition type, I have the field Payt(Payment transaction) checked for my all my conditions.
-In the "Company code dependent settings for product type", I've checked the "Payment details" field.
-In the Main Loan Partner role for the BP, in the company code data, in the payment details tab, I've checked the Payment transaction and payment request fields, and entered information for payment method, housebank payer/ee etc.
Since the posting specification with payment transaction 'X' is not picked, I think something is missing on the payment transaction part.
One other interesting observation is, the moment I changed the FI posting from 4 to 3, the button "payment details" on the top of the screen has disappeared. Previously I used to specify payment details for each flow using the screen that comes off that button. So I assume now the payment details need to be taken care of in the BP/client level or flows level.
I'm not sure where I'm missing one fine detail.
Thanks a lot for your help in advance. I really appreciate it.

Loan postings to vendor accounts

Hi
I am posting employee loan amounts and the recovery to employee vendor accounts.
How ever I would like to know whether is is possible to post to vendor accounts with spI gl indicator.
We have a reco account defined for employee loans, so accounts used to post these loan amounts with sgl indicators.
Now they would like to continue with the same even after payroll going live.
The posting to vendors clearly says that posting with sgl is not possible.
Have any of you come across similar situations and what can be the possible solution or workaround.
regards
sameer

Hi,
You can create the GL account via transaction FS00.
Make sure that rane is ther e as similalr to the personnel no range .
And try to create the GL account with FICO consultant.
Warm Regards,
Kapil Kaushal

Two to Three loan to be posted to vendor account

Hi
I have assinged the symbolic accounts with "K" and in the OBYU assinged to *0002 with the respective symbolic accounts. For example if an employee has festival loan and housing loan when i am posting both loans are adding and appearing in vendor account credit side.
But my requirement is i want to show the respective loan accounts individually with the respective amounts.
How to reslove this
Thanks in advance

Yes For housing loan it is 9000 and for festival loan it is 9020 In fk10 when i am checking it is showing as 3972.60 but actually housing loan is 3,405.93 and vehical loan is 566.67. whereas after manual posting in FK10 clicking on the special GL they are getting the each loan accounts seperately.
Now client wants the same kind of procedure. Whereas in my posting it adding all the loan amounts and sitting in respective vendor accounts.
How to resolve this.
Thnks in advacne

Tables for vendor invoice and payment

Hi Gurus.
I want to know from which tables i can get the information for folllowing points.
1. Vendor Invoices - Complete (Header and Item)
2. Vendor Payments Details Detail about payment method (check, wire, etc)
Please tell me tje table names.

There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
|Table Name |Table Description |
|/BEV3/CHKOMPAZVV |Append Structure CH -> CO PA |
|/CWM/ACCIT |Append Structure for Enhancement of Structure ACCIT in CWM |
|/CWM/KOMP |Catch Weight Management Enhancement |
|/DSD/TAXJURCD |Ship From Tax Jurisdiction Code: for Header Prc Comm Str |
|/SAPNEA/J_SC_LFA1 |Subcontractor Information |
|/SAPNEA/J_SC_LFB1 |Subcontracting Management |
|/SAPPSPRO/A_FI2_LONGNUM |IBU-PS: Append structure for structure NONBSEG |
|/SAPPSPRO/A_LONGNUMBER |additional fields for SPIIN number |
|/SAPPSPRO/EADD |Purchasing Document Header: Additional Data |
|/SAPPSPRO/EADD_DATA |Purchasing Document Header: Data Part Additional Information|
|/VSO/R_KNA1_A |Append to KNA1 for Vehicle Space Optimization |
|/VSO/R_KNA1_I |Additional Data for Vehicle Space Optimization for KNA1 |
|AACCHD_FMFG |US federal fields |
|AACCHD_PSO |IS-PS: ACCHD Append Structure for Payment Requests |
|AACCIT_GM |Append for Grants Management |
|AACCIT_PSO |IS-PS: ACCIT Append Structure for Payment Requests |
|AACCIT_SSP |Append for Payment Statistical Sampling Process |
|AACCIT_USFG |Append structure for US federal government |
|AAUSZ_CLR_USFG |Clearing information for US Fed (Tresury Confirmation) |
|ABKPF_PSO |IS-PS: BKPF Append Structure for Payment Requests |
|ABKPF_UMB |IS-PS: Append Structure for Transfer Transaction FMITPO |
|ABSID_PSO |IS-PS: Data appendix of open items customers |
|ABSIK_PSO |IS-PS: Data appendix of open items vendors |
|ABSIS_PSO |Local Authorities |
|ABUZ |Help Structure for Line Items to be Generated Automatically |
|ACCCR |Accounting Interface: Currency Information |
|ACCCR_FKEY |Key: Acctg Currency Data for Line Item Including Currency |
|ACCCR_KEY |Key: Accounting Currency Data for Line Item |
|ACCFI |Interface to Accounting: Financial Acctg One-Time Accts |
|ACCHD |Interface to Accounting: Header Information |
|ACCHD_KEY |Key: FI/CO Document Header |
|ACCIT |Accounting Interface: Item Information |
|ACCIT_EXTENSION |ACC Document: Additional Item Information |
|ACCIT_JV |Joint Venture Accounting |
|ACCIT_KEY |Key: FI/CO Line Item |
|ACCIT_WT |Withholding tax information for FI Interface |
|ACCRDF |Fields for Posting Small Differences: Preparation |
|ACC_DOCUMENT |Accounting document |
|ACC_KONTEXT |Context Info for FI Single Screen Transactions FB50 and FB60|
|ACERRLOG |Return Parameter |
|ACGL_HEAD |Fields for Document Header Entry Screen |
|ACGL_ITEM |Structure for Table Control: G/L Account Entry |
|ACSCR |Communication Structure for Field Modification SAPLFDCB |
|ACSPLT |Carrier for Split Information re: Current Account Line Items|
|ACSPLT_WTNEW |Proportion of New Withholding Tax |
|ACSPLT_WTOLD |Proportion of Old Withholding Tax |
|ADDR1_SEL |Address selection parameter |
|AEBPP_KNBK |Additional Fields Bank Data Biller Direct |
|AEBPP_LFBK |Additional Fields Bank Data Biller Direct |
|AFMIOI |Append for new fields ECC50/ERP |
|AFMIOI_USFG | SD order needs quantity |
|AFMISPS |Additional Fields for Table FMISPS |
|AFM_ACCIT_EXTENSION |Extension for FM Payment Update |
|AFM_FAGL_GLT0_ACCIT_EXT |Extension FM Account Assignments |
|AFM_FI_BKPF_SUBST |Append to Structure BKPF_SUBST |
|AFM_FMFCTF |Append for Fund Center substrings |
|AFM_FMFINCODE |Append for Fund substrings |
|AIFM01D |Append for IFM01D |
|AKNA1_FMFG |US Federal Government Customer Master Data Additional Fields|
|AKNA1_PSO |Local Authority Additional Fields |
|AKNB1_PSO |IS-PS: Customer Master Record, Additional Data (Co.Code) |
|AKNBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALFA1_FMFG |US Federal Government Vendor Master Data Additional Fields |
|ALFA1_PSO |Local Authority Additional Fields (Address) |
|ALFB1_FMFG |PS fields for company code-specific master data field |
|ALFB1_PSO |IS-PS: Data Appendix Vendor Master Record (Company Code) |
|ALFBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALVDYNP |ALV dialog screen fields |
|ALV_S_FCAT |Field Catalog (for LVC and for KKBLO) |
|ALV_S_FILT |Filter Criteria (for LVC and for KKBLO) |
|ALV_S_GRPL |Group Levels (for LVC and for KKBLO) |
|ALV_S_LAYO |Layout (for LVC and for KKBLO) |
|ALV_S_PCTL |Structure for Checking Print in ALV |
|ALV_S_PRNT |Print settings (for LVC and KKBLO) |
|ALV_S_QINF |Structure for Quickinfos of Exceptions |
|ALV_S_SGRP |Field Groups (for LVC and for KKBLO) |
|ALV_S_SORT |Sort Criteria (for LVC and for KKBLO) |
|ANBZ |Help structure for asset line item |
|ANLZACCOUNT |Additional Account Assignment Objects in Asset Accounting |
|ANLZACCOUNT_FKBER |Account Assignment Objects: ANLZACCOUNT with Function Added |
|ARC_PARAMS |ImageLink structure |
|AT003_XBLNR2 |Append structure for US federal government |
|AUSZ1 |Clearing Table 1 |
|AUSZ2 |Clearing Table 2 |
|AUSZ_CLR |Assign Clearing Item to Cleared Items |
|AUSZ_CLR_ASGMT |Assgt of Clrg Items - Cleared Items with Acct Assignment |
|AUSZ_INFO |Open item data for clearing transactions |
|AVBKPF_FMFG |US federal |
|AVBKPF_PSO |IS-PS: Append Structure VBKPF for Payment Requests |
|AVBSEGDPSO |IS-PS: Append Structure VBSEGD for Payment Requests |
|AVBSEGKPSO |IS-PS: Append Structure VBSEGK for Payment Requests |
|AVIK |Payment Advice Header |
|AVIP |Payment Advice Line Item |
|BALHDR |Application log: log header |
|BALMT |Application Log: Structure for a formatted message |
|BAL_S_CLBK |Application Log: Return routine definition |
|BAL_S_CONT |Application Log: Context |
|BAL_S_MSG |Application Log: Message Data |
|BAL_S_PAR |Application Log: Parameter Name and Value |
|BAL_S_PARM |Application log: Parameters |
|BAPIASCONT |Business Document Service: File Content ASCII |
|BAPIBDS01 |Business Document Service: Reference Structure for BAPIs |
|BAPICOMFIL |BDS: Command File for Transport Entries |
|BAPICOMPO2 |SBDS: Enhanced Component Information |
|BAPICOMPO3 |SBDS: Enhanced Component Information |
|BAPICOMPON |Business Document Service: Component Table |
|BAPICONNEC |BDS: Structure for BDS Links |
|BAPICONTEN |Business Document Service: File Content |
|BAPIDPROPT |BDS: Structure for Properties |
|BAPIFILES |Business Document Services: Transfer Table for File Names |
|BAPIPROPER |BDS: Structure for Properties |
|BAPIPROPTL |BDS: Structure for KPRO Properties |
|BAPIQUERY |BDS Structure for Query Table |
|BAPIRELAT |Business Document Service: Relations |
|BAPIRET1 |Return Parameter |
|BAPIRETURN |Return Parameter |
|BAPISIGNAT |Business Document Service: Signature Table |
|BAPISRELAT |Business Document Service: Relationship Table with Signature|
|BAPIURI |Business Document Service: URI Table |
|BDCMSGCOLL |Collecting messages in the SAP System |
|BDCRUN |Batch input: Runtime analysis |
|BDIDOCSTAT |ALE IDoc status (subset of all IDoc status fields) |
|BDI_SER |Serialization objects for one/several IDocs |
|BDN_FKT |Business Document Navigator: Functions to be Excluded |
|BDWFAP_PAR |Parameters for application function module - IDoc inbound |
|BDWFRETVAR |Assignment of IDoc or document no. to method parameter |
|BDWF_PARAM |Parameters for workflow methods for IDoc inbound processing |
|BKDF |Document Header Supplement for Recurring Entry |
|BKDF_SUBST |Process Interfaces: Substitutable fields during posting |
|BKORM |Accounting Correspondence Requests |
|BKP1 |Document Header Supplement for Update |
|BKPF |Accounting Document Header |
|BKPFBU_ALV |Document Overview: Display Document Headers in ALV Grid Ctrl|
|BKPF_CARD |Credit Card: Append for BKPF |
|BKPF_LINE |Item Category for XBKPF_TAB |
|BKPF_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BKPF_USFED |Append structure for US federal government |
|BLNTAB |Document Number Table for Financial Accounting |
|BNKA |Bank master record |
|BNKAAPP |Appendix to Table BNKA |
|BNKT |Conversion of temporary to internal bank keys |
|BOOLE |Boolean variable |
|BSEC |One-Time Account Data Document Segment |
|BSEC_LINE |Item Category for XBSEC_TAB |
|BSED |Bill of Exchange Fields Document Segment |
|BSEE |Changeable Fields in the Line Item |
|BSEG |Accounting Document Segment |
|BSEGL |Document Segment: Fields Derived for Line Layout Variant |
|BSEGS |G/L Item Transfer Structure for Single Screen Transactions |
|BSEGT |Transfer Table for the Tax Postings to be Generated |
|BSEGZ |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
|BSEG_ALV |Document Overview: Document Item Display in ALV Grid Control|
|BSEG_LINE |Item Category for XBSEG_TAB |
|BSEG_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BSET |Tax Data Document Segment |
|BSEU |Line Item Additional Information (Update) |
|BSEZ |Line Item Additional Information (Online) |
|BSEZ_LINE |Line Item Category for XBSEZ_TAB |
|BSID |Accounting: Secondary Index for Customers |
|BSIK |Accounting: Secondary Index for Vendors |
|BSIP |Index for Vendor Validation of Double Documents |
|BSIS |Accounting: Secondary Index for G/L Accounts |
|BSIX |Index table for customer bills of exchange used |
|BTXKDF |Fields for Exch.Rate Difference Posting for Taxes |
|BVOR |Intercompany posting procedures |
|CACS_A_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_A_CUST_COND |Commissions: Customer Fields Condition Technique |
|CACS_A_FIELDSPRICING |Append for Condition Technique Fields from Commission System|
|CACS_S_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_S_CUST_COND |Condition Attributes |
|CACS_S_FIELDSPRICING |Comm.: All Condition Technique-Relevant Commission Fields |
|CACS_S_FSINS |Customer Fields for Condition Technique of Insurances |
|CCDATA |Payment cards: Database fields relevant to both SD and FI |
|CFW_LINK |CFW: Link Info of a Container |
|CI_COBL |Extension |
|CKI_ACCIT_ML |Transfer from MM to ML in accit-structure |
|CNTLSTRLIS |Control stream list |
|COBK |CO Object: Document Header |
|COBK_ONLY |Non-key fields only in COBK (INCLUDE structure) |
|COBL |Coding Block |
|COBLF |Coding block: Tax table structure |
|COBL_COKZ |Assignment types for CO account assignments |
|COBL_DB_INCLUDE |Include with Additional Account Assignments for DB Tables |
|COBL_EX |Coding Block for External Applications (Not CO/FI) |
|COBL_FI |Fields from COBL that Must not Be Overwritten in FI |
|COBL_FM |Additional Fields for FM |
|D010SINF |Generated Table for View D010SINF |
|D020S |System table D020S (screen sources) |
|D020T |Screen Short Description |
|DBSEG |Dialog Supplementation BSEG (Taxes) |
|DD02L |SAP Tables |
|DD03P |Structure |
|DD03V |Table fields view |
|DD07V |Generated Table for View DD07V |
|DD23L |Matchcode ID |
|DD32P |Interface structure for search help parameters |
|DDSHDEFLT |Description of a default value for search help fields |
|DDSHDESCR |Interface: elementary search helps of a search help |
|DDSHFPROP |Characteristics of search help parameters |
|DDSHIFACE |Interface description of a F4 help method |
|DDSHRETVAL |Interface Structure Search Help <-> Help System |
|DDSHSELOPT |Selection options for value selection with search help |
|DDSUX030L |Nametab Header, Database Structure DDNTT |
|DDSUX031L |Nametab Structure, Database Structure DDNTF |
|DDTYPES |Table of all Dictionary types and classes |
|DFIES |DD Interface: Table Fields for DDIF_FIELDINFO_GET |
|DISVARIANT |Layout (External Use) |
|DOKHL |Documentation: Headers |
|DPPROPS |General property structure for data provider |
|DTC_S_LAYO |Structure for Design of Double Table Control |
|DTC_S_TC |Structure for table controls in the double table dialog box |
|DTC_S_TS |Tab Title Structure |
|DYNPREAD |Fields of the current screen (with values) |
|E071 |Change & Transport System: Object Entries of Requests/Tasks |
|E071K |Change & Transport System: Key Entries of Requests/Tasks |
|EAPS_20 |Field Enhancements for EA-PS 2.0 |
|EDIDC |Control record (IDoc) |
|EDIDS |Status Record (IDoc) |
|EDIFCT |IDoc: Assignment of FM to log. message and IDoc type |
|EDIMESSAGE |Transfer Structure with all Sy Fields for T100 |
|EDI_DS |Status record for interface to EDI subsystem |
|EDI_HELP |Help Structure for Reference Fields in EDI Function Groups |
|EK05A |Communication Area Purchasing - Financial Accounting |
|ESKN |Account Assignment in Service Package |
|EUDB |Development Environment Objects |
|EUOBJ |Workbench: Development Objects |
|EXCLTAB_LINE |Lines of EXCLTAB with OK Code to be Deactivated |
|EXISTING_DOC |Original Document |
|F05ACTRL |Control Fields for SAPMF05A and Subprograms |
|FAGLBSEGL_S |Additional Sender Flds from General Ledger for Doc. Overview|
|FAGL_GLT0_ACCIT_EXT |Line Information for Document Splitting |
|FAGL_MIG_S_BUKRS_LEDGER |Combination of Company Code and Assigned Ledgers |
|FAGL_SPLIT_FLD_S |Characteristics Permitted for Split |
|FAGL_S_APPLICATION |Application and Subapplication |
|FAGL_S_BALDIM |G/L Characteristics of Document Split in New General Ledger |
|FAGL_S_BUKRS |Structure with Company Code |
|FAGL_S_BUKRS_EXT |Structure: Company Codes --> Ledgers |
|FAGL_S_CURTYPES |Currency Types of a Ledger |
|FAGL_S_MIG_001 |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S |
|FAGL_S_MIG_MGPLN_EXT |Structure: Extended Migration Plan Information |
|FAGL_S_T8G40_BS |Split Fields with Characteristic "Balance Sheet" |
|FCRD_VBKPF |Credit Card: Include for Appends for BKPF, VBKPF |
|FCRD_VBSEG |Include for Appends for VBSE* |
|FDM_AR_CASE_ATTR_1 |FSCM DM: |
|FDM_AR_LINE_ITEM |FSCM: DM |
|FDM_AR_RFPOS |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
|FELD |Screen Painter fields (internal) |
|FICCO |Adjustment Values for External Document Items |
|FICCT |Totals Information for Interclient Posting |
|FICTX |Tax Information for ICT |
|FIELDINFO |Field attributes for a specific field |
|FIN1_PARAM |OBNG: Trans. structure for official doc. numbering (global) |
|FIN1_PARAM_FI |OBNG: FI parameters |
|FIN1_PARAM_MM |OBNG: MM Parameters |
|FIPEX_STRUC |Subfields Commitment Item |
|FIPOEXT |Help structure for line items to be generated automatically |
|FIREVDOC |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS |
|FISTL_STRUC |Substructure Fund Center |
|FM01 |Financial Management Areas |
|FMBLSTRING_COMPONENTS |Component of the BL String |
|FMCI |Commitment items master data |
|FMDY |FIFM: Screen Fields |
|FMFCTR |Funds Center Master Record |
|FMFG_ACCIT_EXTENSION |Extention for all fields that have to be transfered into BL |
|FMFINCODE |FIFM: Financing code |
|FMFPO |FIFM: Commitment Item |
|FMHRBA_NEG_DOC_TYPES |HR Integration: Doc. Types for Negative Funds Commitments |
|FMHRBA_SETTINGS |Integration with HR: Settings |
|FMHRBA_VAD_SETTINGS |HR Integration: Generate Value Adjustment Docs for Changes |
|FMICCN |FM: Append Structure for FMIOI (CCN Fields) |
|FMIDATA |Common Data for Funds Management Actual Data |
|FMIDATAFI |Clean FI Data for Funds Management Actual Data |
|FMIDATAOI |Clean Open Item Data for Funds Management Actual Data |
|FMIFIIT |FI Line Item Table in Funds Management |
|FMIKEY |Common Key for Funds Management Actual Data |
|FMIKEYFI |FI - Key for Funds Management Actual Data |
|FMIKEYOI |Common Key for Funds Management Actual Data |
|FMIOI |Commitment Documents Funds Management |
|FMIOIKEY |Key for Table FMIOI |
|FMIOI_USFG | SD order needs quantity |
|FMIREF |Ref. Funds Management Actual Data to Preceding Document |
|FMISPS |General Parameters for Funds Management |
|FMIT |Totals Table for Funds Management |
|FMMRESERV |Include for the Reduction of Funds Reservations (FM) |
|FMRFC |Function Modules and their RFC Destinations |
|FMSP_SPLIT_FIELDS |PSM Fields used in multiple account splitting |
|FMT001 |Additional Customizing for Funds Management |
|FMUP00T |Update Profiles |
|FMUP01 |Update Control with Value Type Dependency |
|FMUP_INV_KEY |Extension for FM Update: FI Key of Invoice |
|FMUP_PAY_KEY |Extension for FM Update: FI Key of Payment |
|FS006 |Fields for Optical Archiving |
|FTCHECK |Foreign Trade: Import Simulation - Ctrl Fields for Pricing |
|FTEXTS |Communication Structure for Additional Components |
|FTGENERAL |Foreign Trade: General Fields Item |
|FUND_STRUC |Substructure Fonds |
|FVD_TZB0A |Append to TZBOA: Loans Fields |
|GLACCOUNT_CCODE |G/L Account Master Record: Company Code |
|GLACCOUNT_CCODE_DATA |G/L Account Master Record: Company Code - Data |
|GLACCOUNT_CCODE_INFO |G/L Account Master Record: Company Code - Information |
|GLACCOUNT_CCODE_KEY |G/L Account Master Record: Company Code - Key |
|GLX_ORG_INFO |Organizational Assignment |
|GMBSEGZ |Grants Management Add-on |
|GXXLT_H |XXL interface: horizontal features |
|GXXLT_O |XXL_interface: texts for online display |
|GXXLT_S |XXL interface: structure of the semantics table |
|GXXLT_V |XXL interface: vertical features |
|HELPVAL |Restrict Value Range - Transfer Table |
|HELP_INFO |Transfer Values for the Help Processor |
|HELP_VALUE |Structure or Function Module HELP_VALUE_GET_FOR_TABLE |
|HHM_COBL |Include for COBL from FM |
|IADDR_PSO |Local Authority Additional Fields (Address) |
|IBKPF_PSO |IS-PS: Include Structure BKPF Payment Request Doc.Header |
|ICDIND |Structures for generating change document update programs |
|ICON |Icons table |
|ICONS |Icons |
|ICURR |Interface for Currency Translation

Vendor line item

Dear All,
My clients wants Spilts in Vendor line items while hitting that particular vendor.
Clearly,
We are giving all Advances like Loan advance, Salary advance to employeees as a vendor and
will deduct, while doing salary process by putting deduction wage type in 14 info type.
While doing Payroll posting 2 documents will be genarated one by one (simply 2 line items) for the same posting run because those 2 symbolic accounts are customized in vendor account in SPRO.
My Quesation and Requirement is,
After do the live Posting, if an employee have 2 deductions, say 2500 advance deduction,1500 Loan deduction (Total 4000 rupees
Will appear in as a one line item if u go for FBL1N transaction.
My client wants 2 line items, one line item shold have 2500 Rupess, Second line item 1500 Rupess,
Then he can strightforward one is for advance deduction, one is for Loan deduction.
is there is any chance to spilt the one vendor line iten which comes from by payroll posting in two.
Please help me on this.
Venkat

Please give any suggesition on this

Vendor Invoices/Customer -BAPI

Hi all
Equivalnt bapis to postVendor Invoices/Customer Invoices through f-02 transaction.
we need to post with and without special GL Indicator. Can anyone let me knw which is the suitable bapi with SAMPLE DATA and MANDATORY FIELDS.
Thanks
sha

Hi,
Pls try these BAPI's...
BAPI_ACC_GL_POSTING_POST
BAPI_ACC_DOCUMENT_POST
BAPI_ACC_GL_POSTING_CHECK
FI_GET_POSTING_KEY
BAPI_ACC_GL_POSTING_POST
More Information about this:
Text
Accounting: General G/L Account Posting Functionality
You can use this method to update business transactions in Accounting which mainly affect the general ledger and are definitely not updated in subledgers which are relevant to the balance sheet.
An example of this is a provision posting for an expected guarantee service.
This can be produce debit or credit entries to balances which are not managed in one of the subledgers relevant to the balance sheet. This is especially applicable if the balances cannot be represented as assets, customers/vendors, materials, loans, etc.
An example of this is a provision posting for an expected guarantee. However, this can also involve depreciation or write-ups in which values have a higher level of summarization than in the corresponding subledger relevant to the balance sheet in which they are managed.
An example of this is foreign currency revaluation for receivables/ payables caused by considerable exchange rate fluctuations which is not updated in accounts payable or accounts receivable.
A similar transaction may come about when revaluating balances for raw materials if the revaluation takes place at a corresponding level of summarization.
The third cateogry is the reclassification of items to balance sheet accounts or income statement accounts, which is only undertaken in the general ledger in order to balance accounts (values are then finally reassigned to financial statement items).
Example: Reclassifying balances of receivables with different return times for the balance sheet.
Restrictions:
This object cannot be used to update business transactions which are normally posted to one of the subledgers which affects the balance sheet (such as a billing document; for this see the business object AcctngBilling).
This is especially applicable if the reason the relevant subledger cannot be updated is because it is an external system or is not in use.
Notes
If the currency fields have been entered in the CurrencyAmount parameter, the system runs a complete check for the document. Otherwise only the account assignment objects are validated.
Messages are displayed in the Return parameter. You will find the return values and their meanings in the documentation for this parameter.
Further Information
For further information, see the documentation on "Interfaces to Accounting" in the R/3 Library (under "Cross-Application Functions -> Interfaces to External Systems").
Parameters
DOCUMENTHEADER
OBJ_TYPE
OBJ_KEY
OBJ_SYS
ACCOUNTGL
CURRENCYAMOUNT
RETURN
EXTENSION1
Exceptions
Function Group
ACC4
http://www.planetsap.com/LIST_ALL_BAPIs.htm
Re: BAPI FOR POSTING FBS1 TRANSACTION
***Reward Points if Useful
Regards
Gokul

Interest calculation on secured loans

Hi guys,
I have a customer invoice at 1000 rs after that i have been paid to customer for 5000 rs. The difference amount of 4000 rs (5000 - 1000 ) we have considered as a secured loan. So how can i calculated the interest on the 4000 rs only.
Please let me know the configuration steps with documentation.
Thanks
Ram

HEllo!
In the report RFINTITAR, you use the interest indicator customizing:
IMG   > Prepare Item Interest Calculation   > Ref. Date
(table V_T056UX)   > field Ref.
(FI Item Interest Calculation: Reference Date)
You have the possibility to define what You need to be considered as
incoming payment due date, choosing between:
1 Value Date (or Baseline Date for Net Payment)
2 Document Date
3 Posting Date
4 Payment Baseline Date
As you can use one interest indicator per customer/vendor you can use only of the dates is used. But, in this
program you can use the BADI FI_INT_CUS01. Please, check if you can meet your business requirements using the methods
of the BADI.
REgards,
REnan

Interest calculation on bank loan

Hi guru,
we have taken long term loan from 10 banks.we have to calculate interest on loan from each bank.we have maintained each bank loan a/c as a vendor.As we know the procedure as given by sap for balance interest calculation will be followed here.is it correct or not.one more doubt is whether treating each loan a/c as a vendor is correct or not.
Thanks
shivaji

Hi,
Here you need Balance interest calculation.
Balance interest calculation used for bank loans. It calculate GL balance only
it will take particular period and need to configure document type SA.
Item interest calculation used for item wise calculations like vendor wise and customer wise. It depends on payment terms and in this GL accounts Select open item management.
I hope it is cleared.
Thanks & Regards,
Haribabu Bodapudi

Posting on vendor reconciliation account in FS-CML

Hi experts,
I am currently trying to prepare a Proof of concept for my customer on FS-CML on an IDES system. They want to manage the loans they contracted with banks.
In fact, when posting the repayment or interests, they want to write directly on the credit of the reconciliation account (type K) linked to the vendor of the partner.
To achieve this, I changed the setup on transaction FNZA on Transaction Type “1110” and I replaced the credit posting key “50” by “31”. I also replaced the posting category “45” by “42” and I put the reconciliation account (type K) on the account symbol “5.2.2”.
After doing all of this, when I launched transaction FNM1S on the loan contract, I got the following error : « No account is specified in item 0000000003 ». (The vendor code should be on the LIFNR field, which is not).
Am I missing something ? Is there any other setup to put in place ? Or do I need to link the Loan contract / Partner / Vendor in a certain way ?
Thanks for your responses.

Here is the detailled message I am getting from SAP :
No account is specified in item 0000000003
Message no. F5670
Diagnosis
No account was specified for account type "K" in item "0000000003" of the FI/CO document.
System Response
The Financial Accounting program cannot process the document.
Procedure
A system error has probably occurred in the application you called up. Check the data transferred to item "0000000003" of the FI/CO document.

Vendor Loan

Similar Messages

Maybe you are looking for