FSCM - table v_ukm_item

Hi,
The commitment value on sales orders in FSCM credit management (transaction ukm_bp) is collected from table v_ukm_item. Does anyone know which field on the sales order the field AMOUNT is collected from? I'm guessing it should be one of the fields in the conditions tab on the sales order, but I cannot figure out which..
Regards,
Solveig

Hi.. I Prepared a list of the item categoreis tha were missing in the table V_TVEPZ__V and found that those item catotires are missing which do not reuqire any schedule lines or for those items which are not required for Transfer of requirements.
for ex. Rebate Credit memo request Item cats do not require any TOR to happen for them, serive order items which do not require TOR.. i found some 44 item cats in standard system which are missing in the table mentioned by you..
I am not sure on the exact logic how sap system filtered those item caterues but looking at the Description of those Item categories.. i am very sure that those filtered Item categires are not used for TOR... or availability check...

Similar Messages

FSCM tables

Hi,
Does anybody have documentation regarding to FSCM tables? We are using SAP NetWeaver and would like to enhance FSCM Credit- and Collections Management with custom fields, but not sure which tables to extend.
E.g.: in CollMan we would like to push the data from FI to FSCM per Company Code and use it in FSCM for Collection Rules, etc.
Thanks in advance,
Andras D.

I am guessing this is an ABAP or FI query?
Please post in the relevant forum to get responses.
This forum is for certified professionals or those who want to take certifications / training in SAP.
Cheers!
Zub

After creating Peopletools 8.52, FSCM 9.0 Demo PSSTATUS table shows 8.48

Hi
I am building the new demo environment for Finance.
PeopleTools 8.52
FSCM 9.0
on unicode database with Demo option. But running the datamover scripts, PSSTATUS table still shows 8.48.
Any Ideas ?
Thanks,
Sarathy K

Actually the reason why it is showing 8.48 is because FSCM 9.0 have application database version 8.48 and you are installing peopletools 8.52 so you need to update your database setup by running some peoplesoft delivered sql scripts.
Refer the installation guide for Peopletools 8.52 http://docs.oracle.com/cd/E26530_01/psft/acrobat/PeopleTools_8.52_Installation_Oracle.pdf
In chapter 7 the very first topic describes it very well.
In short go to PS_HOME\scripts
and find following scripts...
Required Scripts for Non-Unicode Databases
rel849, rel850, rel851, and rel852
Note. If you are installing a 9.0 or higher application, run rel849n, rel850n,
rel851n, and rel852n instead.
Required Scripts for Unicode Databases
rel849u, rel850u, rel851u, and rel852u
Note. If you are installing a 9.0 or higher application, run rel849un, rel850un,
rel851un, and rel852un instead.
Gaurav

How to set up FSCM 9.0 Application for Customers to use ?

Folks,
Hello. I have just installed FSCM 9.0 ( all of its modules) and run the application in Browser successfully. The Database is a clean System Database without any Demo data (Production Database).
In order for Customers to type in their data into the application, we need to set up CharFiled, SpeedType, SetID, common data in Controls Tables in the Database. In Menu, there is "Setup Financial/Supply Chain", and under PeopleTools, there is "Setup Manager". But I don't understand where to start to set up the application FSCM 9.0 application.
Do any folks understand the procedure to set up FSCM 9.0 application for Customers to use step by step ?
Thanks.

Folks,
Hello. Thanks a lot for replying.
I have installed FSCM 9.0 all of 50 modules. I just want to implement General Ledger module. Thus, I create a project named "General Ledger" in Setup Manager under PeopleTools as follows:
PeopleTools -> Setup Manager -> Manage Implementation Project -> Create New Project by Product -> select "General Ledger" ->View Summary -> Save -> Type in "General Ledger" in Project Name Box -> Click ok -> click "generate setup tasks" -> click "setup task generation status"
It has been for a long time, I still see "Run Status" is always "Queued". The button "View Setup Task" does not become clear. This means the process is not completed.
Do we need to configure Process Scheduler at first before run Setup Manager ? If yes, how to configure Process Scheduler for Setup Manager to generate a list of setup tasks of a project ?
Thanks.

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

FSCM-COL program FDM_COLL_SEND_ITEMS checks business partner in KNA1

We have a requirement to create a Business partner in FSCM-COL without creating any Customer master in FI (KNA1 table). For each Customer invoice we have populated the Business partner (UDM_BP) in a free field (BSEG table). Say customer ABC invoice #10000 will have the business partner XYZ assigned in BSEG field XREF1. XYZ is not created as Customer in KNA1 but is created as Business partner in UDM_BP only.
For sending FI-AR data to FSCM, we have changed the BADI logic of determination of Branch/Payer to get the Business partner from BSEG-XREF1 field not from KUNNR. When FI-AR data is sent to FSCM using the program FDM_COLL_SEND_ITEMS, system checks whether Business partner XYZ is created in KNA1 table. Is there any way to avoid creating XYZ as Customer in KNA1 since we would be duplicating 5k+ customer records.
Request your ideas on this.
Thanks,
Siva Parvathala

Hi,
This is kind of strange as to why you want to do this. Anyway you have 1 customer in FI-AR for whom you are generating the invoices. So there is already a customer ABC. You also have a BP XYZ. Now why not use the standard itself and link the customer ABC with XYZ which is going to save all the efforts required for custom modifications. For linking BP and Customer, it is not necessary that both should have the same number range.
Also I don't think you can do the transfer without linking customer and BP. Anyway I will check this and let you know. But I am sure this is redundant work and you can use the standard itself for this.
Regards,
Ravi

FSCM-COL: Adding a new field to Worklist

Hi,
I have a business requirement where the client wants to have the option field of, manually, giving a new status for the invoice (on the u201CInvoicesu201D tab).
So, for him be able to do that I need to add a new column for he be able to select the status for the invoice.
Know, my question is this, do you guys know any enhancement badi that can be used/changed for that requirement ?
For example, this one UDM_WL_ITEM_CREATE_C...Can it be used for this...?
Thanks in advance.
Best Regards,
Bruno Sousa
Edited by: Morbius on Sep 28, 2010 7:32 PM

Morbius - If I get you business case correctly, reqmnt is to add a editable/modifiable field on the Invoice tab where the User can enter manually/select from a drop down list for a particular field?
If ans is yes to above, please elaborate on the requirement, since I feel you could achieve such a feat either thr a P2P in Collections or in F-AR itself.
As per my knowledge of FSCM goes, you can add fields on "Invoice" tab but that one cannot be an editable field. You can add an additional field (I mean, a key figure from FI-AR document from 5 tables, dont remember tables on top of my head) on "Invoice" tab. To implement this, you will have to implement a couple of BAdIs. Step by Step documentation to do this is embedded in a doc in the Media Library under FSCM on SAP portal. As a side note, any addtional field really impacts the performance of Process Recievables screen and is there not recommended by SAP.

FSCM via WS-RM (without PI ) - Update termination issue

Hello experts .
We are trying to integrate SD with FSCM ( credit management) using WS-RM (without PI).
Details of the issue and steps followed so far.
Ideal Scenario :
Once we create / change a sales order ( in SD ) , the interface Creditworthinessquery_out (WS Consumer ) gets triggered (in SD) and the subsequent response CREDITWORTHINESSQUERY_IN(Provider) is triggered from FSCM (with the details of creditworthiness).Once the query response in received an notification is triggered from SD to FSCM (asynchronous service).
After receiving the query response the functionality of credit check happens while creating / changing the sales order .
Configuration steps followed in SOAMANAGER
We have created end points for all the relevant service interfaces (Providers) , and also created logical ports for the respective consumers.
During the creation of logical ports - for the consumers we used the WSDL (of the providers) as the inbound message action.
(This has been done to all the services query , notification that are relevant in our integration).
Current behavior / issue .
While creating sales order the sales order is not getting saved (getting updated in the database).System allows us to complete the sales order creation process and also we get a message as sales order saved successfully. But then there is a update terminated express document that pops up. Sales order is not getting updated in the database.
When I see the logs/traces in SOAMANAGER I see that the query out is successful , query in has the right response (in warning state though) . But no notification is being triggered ?? 
How to overcome this update termination issue ?
When we see the SM13 log , it points to SLD issue (LCR 010: Internal error in SLD API). why do we need a SLD without PI

Hi ,
Finally we are able to solve the update termination issue . But again we are using a work around .
Situation :
Once we executed the VA01 transaction we were getting update termination issue . After lots of debuggung we found that system was trying to get the Business system details ( Own business system data ) . The table lcrt_clntcache had no values.
Solution
We inserted appropriate values in the Table LCRT_CLNTCACH (business system data ) and now it works .This is a work around we got as of now.Credit checks are happening successfully and also integration is good .
(typically if we define business system in SLD (PI) , and run SLD_CHECK , this table gets populated , but in our case we are not using PI instead we are using WS-RM)
But now few questions arise .
a) Why do we need a business system in case we are not using PI ( typically we define business system and technical system in PI ) and instead using WS-RM ?
b) Is it a good practice to update the table ( as did in workaround above )?
c) Is this any bug and needs to be consulted with SAP ?
Please let me know your views .
Edited by: Vedula Adeep on Jan 16, 2012 8:42 AM

FSCM-CR - Extension of Payment Behavior KPI

Hi,
I would like to confirm the capability of extend Payment Behavior KPI's via report UKM_TRANSFER_VECTOR. For example, would it be possible to calculate and send for example the following KPI's, in addition to the standard ones?
- Open items balance, Due balance, Overdue balance, Days in arrears, any other KPIs calculated and stored in Z tables.
Thanks,
Gonçalo

Hi -
I'm doing the same thing on a project I am working on now...client wants additional information (KPI's if you will) - among the things they are looking for are precisely the things you mentioned (in terms of KPI's)
We looked at attaching it to the Payment Behaviors tab. Here is what it would have involved:
- A new .APPEND structure to UKMBP_VECTOR_IT to store your custom fields
- A change to UKM_TRANSFER_VECTOR to update the new fields
- A new view on the Payment Behaviors tab along with the logic to fetch the new data from UKMBP_VECTOR_IT
As you can see, there certainly is customization/ehancement to be had here. It is more than activating a BAdI.
We considered other options but ended up settling on creating an entirely new tab in FSCM CM for the customer-specific data. The development/enhancement steps are similar:
1. Brand new Ztable modeled after UKMBP_VECTOR_IT - including the same key structure
2. Cloned UKM_TRANSFER_VECTOR verbetim - changed the logic to address precisely the fields we needed - the new ones of course.
3. A couple of new views in FSCM CM at the credit segment level. This was a lot of fun getting them hooked up to the menu structure (NOT!) - but I did it. (Geez, the crap looks like it was delivered by SAP...but it wasn't).
The goal of isolating this stuff on to its own tab was to completely isolate the enhancement in case SAP decides to step on it in the future.
Hope this helps.
Dan

FSCM 9.0: COBOL program does not post a Journal into Ledger correctly

Folks,
Hello. I am working on FSCM 9.0 General Ledger module. To FSCM 9.0, we need to compile COBOL by ourself.
I downlaod and install "MS Visual Studio 2005 professional" and "Micro Focus Net Express 5.0". Then compile COBOL successfully. The executable files are copied to PS_HOME\CBLBINU.
Editing Journal is working correctly as follows:
General Ledger > Journal > Creare/Update Journal -> Add -> Line -> Edit Journal ->Process, Total amount comes up correctly and Journal status becomes "V". All debit accounts and Credit accounts are posted into Database PS_JRNL_LN table correctly.
But posting Journal is not working correctly as follows:
In Journal Line page, after select Post Journal -> Process, Journal status becomes "P". But when check Database table PS_Ledger using select * from PS_LEDGER, only Debit accounts of a journal are posted into PS_LEDGER table, all Credit accounts of a journal are not posted into PS_LEDGER.
Because posting a journal into PS_LEDGER table only debit accounts and no credit accounts, all general reports, such as Trial balance, cannot be generated.
Thus, my questions are:
First, does COBOL program GLPPPOST.exe have a problem ? If yes, how to solve it ?
Second, do I set up something incorrectly in General Ledger module and cause only Debit accounts of a journal are posted into PS_LEDGER table and not Credit accounts ?
Thanks.

Folks,
Hello. The question is solved by myself. Thanks.

Fscm ageing report

Dear experts,
We have implemented the FSCM functionalities: Credit and Collection Management.
what is the FSCM report for ageing? We know ukm_bp_display, is it the only one?
We wish that the ageing reports start calculating it from invoice
expire date and not from the sales document date. There is a report that makes it like this?
thanks
Beste Regards
Laura

Dear Remya,
If you are asking for aging buckets ex <=30, 31- 60 , 61-180 days , these information are calculated on real time, based on formula , i dont think so it is stored in tables ,
Formula for this will be , Baseline date + payment terms days = Net Due date ,then Net due Date - Open item date (for which report is executed ) will be the Net due days, which will be shown in respective buckets.
kindly let me know if you need any more details.
thanks and regards
Praveen.J

National Stock Number (NSN) as an Alternate Item Number in PeopleSoft FSCM

My company is a supplier of defense related products to the United States military and sometimes foreign militaries.
The Defense Logistics Agency of the Department of Defense assigns items IDs to material which the United States military buys, transports, stores and uses. These item IDs are called National Stock Numbers (NSN).
My company has a requirement to display (show) the NSN on shipping documents to any shipments for the United States military. Also, we internally in the company need to be able to search the items (and products) by NSN on various screens within Peoplesoft. We also need the ability to periodically load a csv file into peoplesoft to assign NSNs to item IDs.
We are on PeopleSoft version FSCM 8.9. Of course FSCM 8.9 does not have any build-in/delivered functionality to support NSNs. NATO also uses a similar idea called NATO Stock Number. Both the (National Stock Number and the NATO Stock Number) are 13 digits.
I reviewed the 9.1 Peoplebooks and there is no mention of NSN (NATO stock number or national stock number).
I have also reviewed the 9.2 Pre-Release Notes and there is no mention of NSN (NATO stock number or national stock number).
We have thought about using PROD_ITEM.PROD_FIELD_C30_A as a place to store NSNs. We are also considering MASTER_ITEM_TABLE.ITEM_FIELD_C30_A as a place to store NSNs. Please note that we need NSN for shippable products only.
I am looking for better ideas here or at least validate our idea for putting it in the fields discussed above. Also, if someone could give a reason for Product Item table vs Master Item table, which would be better?
Thanks in advance.
Mansoor H. Khan
Principal Programmer Analyst
Thales Communication Inc.
22605 Gateway Drive
Clarksburg, MD, 20871
Tel: 240 864 7747

My company is a supplier of defense related products to the United States military and sometimes foreign militaries.
The Defense Logistics Agency of the Department of Defense assigns items IDs to material which the United States military buys, transports, stores and uses. These item IDs are called National Stock Numbers (NSN).
My company has a requirement to display (show) the NSN on shipping documents to any shipments for the United States military. Also, we internally in the company need to be able to search the items (and products) by NSN on various screens within Peoplesoft. We also need the ability to periodically load a csv file into peoplesoft to assign NSNs to item IDs.
We are on PeopleSoft version FSCM 8.9. Of course FSCM 8.9 does not have any build-in/delivered functionality to support NSNs. NATO also uses a similar idea called NATO Stock Number. Both the (National Stock Number and the NATO Stock Number) are 13 digits.
I reviewed the 9.1 Peoplebooks and there is no mention of NSN (NATO stock number or national stock number).
I have also reviewed the 9.2 Pre-Release Notes and there is no mention of NSN (NATO stock number or national stock number).
We have thought about using PROD_ITEM.PROD_FIELD_C30_A as a place to store NSNs. We are also considering MASTER_ITEM_TABLE.ITEM_FIELD_C30_A as a place to store NSNs. Please note that we need NSN for shippable products only.
I am looking for better ideas here or at least validate our idea for putting it in the fields discussed above. Also, if someone could give a reason for Product Item table vs Master Item table, which would be better?
Thanks in advance.
Mansoor H. Khan
Principal Programmer Analyst
Thales Communication Inc.
22605 Gateway Drive
Clarksburg, MD, 20871
Tel: 240 864 7747

PeopleTool 8.49 and FSCM 9.0 on Oracle 11g issue

Dear All,
I have problem with FSCM 9.0 on oracle database.
I have setup PeopleTools successfully on the same server (Windows 2003 server, SP2)
- IBM Webshpere 6.1
- PeopleTools 8.49
- People FSCM 9.0
- Tuxedo 9.9
- Oracle 11GR1
- I create and import database by manual on user SYSADM, database FSDMO
- I login to Data Mover by SYSADM/SYSADM, import database FSCM database, Data Type: Demo
- Run import script.
My problem are:
- Failed SQL stmt:INSERT INTO PSMSGCATDEFN (MESSAGE_SET_NBR, MESSAGE_NBR, MESSAGE_TEXT, MSG_SEVERITY, LAST_UPDATE_DTTM, DESCRLONG) VALUES (:1, :2, :3, :4, TO_TIMESTAMP(:5,'YYYY-MM-DD-HH24.MI.SS.FF'), :6)
I alter this table by command
alter table PSMSGCATDEFN modify MESSAGE_TEXT varchar2(200);
and run script import again. Another error happen:
- File: e:\pt849-904-R1-retail\peopletools\SRC\pssys\rdmfld.cppSQL error. Stmt #: 350 Error Position: 480 Return: 3113 - ORA-03113: end-of-file on communication channel Process ID: 3284 Session ID: 135 Serial number: 275
Failed SQL stmt:SELECT FIELDNAME, LABEL_ID, LONGNAME, SHORTNAME, DEFAULT_LABEL FROM PSDBFLDLABL WHERE FIELDNAME IN (SELECT A.FIELDNAME FROM PSDBFIELD A, PSRECFIELD B WHERE B.RECNAME = :1 AND A.FIELDNAME = B.FIELDNAME) ORDER BY FIELDNAME, LABEL_ID
This error make the Data Mover hang on. I must kill this process.
Current now, My solution is change this line on sqlnet.ora:
old:
SQLNET.AUTHENTICATION_SERVICES= (NTS)
new:
SQLNET.AUTHENTICATION_SERVICES= (NONE)
and restart listener.
Start Data Mover and run import again.
I don't know where to start again and must start from the begin. I do not know does it delete and import again or not? Does it can solve my problem when I change above line on sqlnet.ora?
I do not know is there anybody have the same problem?
How can I fix it?
Many thanks anybody.
Best regards,

Dear Nicolas,
Thanks for your answer.
I think the error of MESSAGE_TEXT is becuse of UTF8 database. I setup database default encoding is UTF8, but I import FSCM database is nonunicode.
I have another problem after I fixed the error of MESSAGE_TEXT.
Here is the message:
Updating statistics for ZONE_INV
SQL Successful - INSERT INTO PS.PSDBOWNER VALUES('FSDMO', 'SYSADM')
SQL Successful - UPDATE PSSTATUS SET OWNERID = 'SYSADM'
SQL Successful - UPDATE PSOPRDEFN SET SYMBOLICID = 'SYSADM1', OPERPSWD = OPRID, ENCRYPTED = 0
Error: SQL execute error for UPDATE PSACCESSPRFL SET ACCESSID = 'SYSADM', SYMBOLICID = 'SYSADM1', ACCESSPSWD = 'SYSADM', VERSION = 0, ENCRYPTED = 0
Ended: Fri Nov 13 11:42:33 2009
Unsuccessful completion
I don't know what is the error because I can not see the error. I have checked this table and see It have data:
select * from PSACCESSPRFL;
result:
SYMBOLIC VERSION ACCESSID ACCESSPSWD ENCRYPTED
sa1 1 kCTsQ7kCrag= kCTsQ7kCrag= 1
SYSADM1 1 sBzLcYlPrag= sBzLcYlPrag= 1
Can you help me what should I do now? How can I restart from the error?
It run very slowly, more than two days but not finish. Total are 21333 tables.
I don't know is it finish? why it have error?
Thank so much.
Toan Dang

Which SAP tables does CM read to update data

Hi
Please can someone tell me which SAP tables in FI, MM and SD that SAP Cash Management (CM) selctes data from when updating FSCM-CM.
In other words, if I delete CM data and then recreate it using programs RFFDDL00 (delete) and RFFDKU00 / RFFUEB00 / RFFDMM10 / RDDSD10 / RFFDMM20 (create for OIs, GLs/Bank Bal, MM/POs, SD/SOs and MM/PRs resp) which tables are the source tables for SAP CM?
Thanks for any help anyone can give me. I'm trying to undesrstand the data creation process to trace why the drill-down to AP/AR OIs is not working and why the GL drill-down lists 000's more OIs than the CM balance shows and why the drill-down for POs/PRs in MM and SOs in SD works correctly.
Wayne

Hi Priyanka,
Please take a look at these..
http://help.sap.com/saphelp_erp2005/helpdata/en/04/964e38533e3860e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/5a/5b5738ed5a1d36e10000009b38f889/frameset.htm
cheers,
Prashanth
P.S Please mark helpful answers

Contents of table BSIS-BUZID (line item ID)

Dear all,
What mean of T, W and blank in field BUZID (line item ID) from table BSIS.
Thanks very much.
Best Regards,
Koesdianto

Hi,
Use in invoice verification/inventory management
Buzid             Use
8                " Revaluation
A                " Asset
B                " Warehouse stock order
C                " Warehouse stock order assigned
K                " Vendor
F                " Delivery costs
G                " Assigned delivery costs
H                " Delivery costs - warehouse stock order
I                " Delivery costs - assigned warehouse stock order
L                " Warehouse order
M                " Material
N                " Assigned order
P                " Price difference
S                " General G/L account
T                " Tax
W                " GR/IR item
X                " Purchase order - assigned asset
Y                " Delivery costs - assigned asset
Z                " Cash discount clearing
Use in FI:
Special feature: Not just used to indicate G/L accounts; also used for special open items
BUZID         KOART               Use
A             D;K                Statistical offsetting posting (Sp.G/L)
P             D;K                Payment requests
U             S                  Valuation adjustments for reversal
R             D;K                Residual item transfer posting
E             D                  FSCM Biller Direct
D             S                  Bill of exchange discounting
S             D;K                Bill of exchange charges
W             S                  Bill of exchange tax
Regards,
Eli

FSCM - table v_ukm_item

Similar Messages

Maybe you are looking for