PCA balancing - A0 document type in period 14

Hi
We are on 4.7 and trying to create a PCA document with document type A0 in special posting period 14. However, the system does not accept this period. Period 14 is open for + and S in OB52.
Any help with this is greatlly appreciated.
Thanks
NW

Is the special period 14 open in the controlling are check OKKP.
Assign points if helpful

Similar Messages

Trial Balance - Disregard Document Type

Hello Experts,
I have few questions about the disregard document type selection in the trial balance report (S_ALR_87012310). We tried to exclude several document types on this report and the result, transactions having this doc types are displayed under Disregarded Account Transactions by Document type. However the exclusion of doc type doesn't seem to affect the values shown on the trial balance. I am aware that the balances shown on this report came from FS10N (GL account balance display). My question is: What's the purpose of excluding a doc types on this report if it does not affect the values of the trial balance.
Thank you!
Jack

Hi Steven,
Its not possible to view TB in document currency but you can view it in company code currency only. Document currecny will differ from local currency (*co code currency) for certain docs. So the report willnot be able to fetch the correct results.
Hence you have to run TB and Financial statements only in company code currency.
Hope this helps. Pls assign points if helpful
regards,
radhika

ASKB(N): document type do not defined

Hello all!
When I start ASKBN befor AFAB (sistem 6.0) I got a message "Document type for periodic APC posting does not exist". Message no. AC197
But when I went to OBA7 and look through the type AN with Net asset posting and tried to define the interval for it in FBN1, this interval was already exist and 4 document was posted. I set this interval for aquisition postings (abso). What to do with ASKBN? Or what document type should be defined for ASKBN?

Hi,
Go to IMG and assign the document type in the Path:
Asset Accounting - Integration with General Ledger - Post APC values periodically to the General Ledger - Specify Document type for peridical Posting of Asset Values.
Thanks,
Raja.

How to block one of the purchasing document types for certain period

My client asked me to block the one of the purchase order documents for certain period.In what way i can do it? and also it shouldn't be displayed in the purchase documents list when we do me21n?
Advanced thanks,
Sateesh

Hi Sateesh,
Here u cann't block the Document type,
U can do this,only the way to delete that document type for certain peroid.
Thanks & Regards
Suresh
> My client asked me to block the one of the purchase
> order documents for certain period.In what way i can
> do it? and also it shouldn't be displayed in the
> purchase documents list when we do me21n?
>
> Advanced thanks,
> Sateesh

Document type UDO ignoring Period field

Hi all:
I have a document type UDO that includes the automatically created "Period" field which links to financial periods (OFPR). However, apparently I cannot modify it in my form, as no matter what I write into the field the database always ends up with the current period number, instead of the one corresponding to the date I have in my form.
The field is correctly databound as it shows the saved values correctly.
The field is also set correctly by the add-on through code in OnBeforeFormDataAdd before being saved into the database (depending on date selected in a specific field).
The problem is, that even though I am not depending on that field, if the current period is locked, my add-on cannot be used to enter data for another (previous or future) period, because B1 automatically rejects the document when saving ("Period is locked").
Any ideas on this?
Thanks,
Joerg.

I don't have a problem using that field. The problem is that it does not accept what I set it to. It's always saved with the current period number, not the one I tell it to use (the one corresponding to the date used in my UDO document).
As for document type UDO, yes, the add-on is already installed at several clients, I can't just go ahead and change the UDO type. Plus I am using some of the features that come with that type of object (document numbering being one).
As for unlocking the finance period, I haven't tried it but I guess that wold only work if the user has permission to do so, and I couldn't count on that...
Joerg.

Balance report and document types

Hi:
Just one simple question. I am not a FI, but I need to get Balance report, but I need to select only several Document Types. Is this possible?
Do you know this kind of report?
Thanks very much in advanced.
Regards

Hi,
Balance reports are based on totals, while document type is an attribute of a single document. You can produce such a report only based on the documents' tables, e.g. FBL3N report, but not on totals where the balance is calculated.
Regards,
Eli

Period is closed for posting or correct document type is not being used

Hi All,
I am trying to post transaction in AB01. But i am getting below error.
I have checked OB52 and the periods for "+" & "A" are open for 2012.
Error:
Period is closed for posting or correct document type is not being used.
Please assist

document type i am using is AA.check it other side entery documenttype period open or not

Restrict the user   based on document type on migo transaction-prepare GRN

Hi,
We are running ECC6.0 R/3 system.We had a requirement as follows
In MIGO transaction , we want to restrict the user on document type i.e. we want that a particular user can prepare GRN for document type STO only. He cannot prepare GRN for other document type.
We checked SU24->maintain check indicators for transaction codes->enter migo->execute->check indicator.This returned us the authorisation objects present in Migo transaction.We checked the help of all these objects,but none of them we found suitable for above mentioned requirement.We were planning to find out the proper authorisation object to add to Profile generater.
The following is the objects which we have checked for.
A_B_ANLKL-->     Asset Postings: Company Code/Asset Class
A_B_BWART-->     Asset Postings: Asset Class/Transaction Type
B_USERSTAT-->     Status Management: Set/Delete User Status
B_USERST_T-->     Status Management: Set/Delete User Status using Process
C_AFKO_AWK-->     CIM: Plant for order type of order
C_CACL_DSG-->     Interface Design
C_DRAW_BGR-->     Authorization for authorization groups
C_DRAW_DOK-->     Authorization for document access
C_DRAW_TCD-->     Authorization for document activities
C_DRAW_TCS-->     Status-Dependent Authorizations for Documents
C_KLAH_BKP-->     Authorization for Class Maintenance
C_STUE_BER-->     CS BOM Authorizations
C_STUE_WRK-->     CS BOM Plant (Plant Assignments)
C_TCLA_BKA-->     Authorization for Class Types
C_TCLS_BER-->     Authorization for Org. Areas in Classification System
C_TCLS_MNT-->     Authorization for Characteristics of Org. Area
F_BKPF_BUK-->     Accounting Document: Authorization for Company Codes
F_BKPF_BUP-->     Accounting Document: Authorization for Posting Periods
F_BKPF_KOA-->     Accounting Document: Authorization for Account Types
F_FICA_FOG-->     Funds Management: authorization group of fund
F_FICA_FSG-->     Funds Management: authorization group for the funds center
F_FICB_FKR-->     Cash Budget Management/Funds Management FM Area
F_KNA1_APP-->     Customer: Application Authorization
F_LFA1_APP-->     Vendor: Application Authorization
F_SKA1_BUK-->     G/L Account: Authorization for Company Codes
G_GLTP -->       Spec. Purpose Ledger Database (Ledger, Record Type,
                               Version)
J_1IDEP_SL-->     Authorization object for depot sale transaction
J_1IEXC_OT-->     Authorization object for Other Excise Invoice Create
J_1IEX_PST-->     Autorization object for posting Other Excise invoice
J_1IGRPT1-->     Auth. for PART1 at GR
J_1IINEX -->            Incoming Excise Invoice
J_1IRG23D-->     Authorisation object for Depo Transactions
K_CCA-->                     CO-CCA: Gen. Authorization Object for Cost Center
                                Accounting
K_CSKS     -->                CO-CCA: Cost Center Master
K_CSKS_SET-->     CO-CCA: Cost Center Groups
K_PCA-->                    EC-PCA: Responsibility Area, Profit Center
L_TCODE-->                    Transaction Codes in the Warehouse Management System
M_ANFR_BSA-->     Document Type in RFQ
M_ANFR_EKG-->     Purchasing Group in RFQ
M_ANFR_EKO-->     Purchasing Organization in RFQ
M_ANFR_WRK-->     Plant in RFQ
M_BEST_BSA-->     Document Type in Purchase Order
M_BEST_EKG-->     Purchasing Group in Purchase Order
M_BEST_EKO-->     Purchasing Organization in Purchase Order
M_BEST_WRK-->     Plant in Purchase Order
M_MATE_CHG-->     Material Master: Batches/Trading Units
M_MATE_STA-->     Material Master: Maintenance Statuses
M_MATE_WRK-->     Material Master: Plants
M_MRES_BWA-->     Reservations: Movement Type
M_MRES_WWA-->     Reservations: Plant
M_MSEG_BMB     -->Material Documents: Movement Type
M_MSEG_BWA-->     Goods Movements: Movement Type
M_MSEG_BWE-->     Goods Receipt for Purchase Order: Movement Type
M_MSEG_BWF-->     Goods Receipt for Production Order: Movement Type
M_MSEG_LGO-->     Goods Movements: Storage Location
M_MSEG_WMB-->     Material Documents: Plant
M_MSEG_WWA-->     Goods Movements: Plant
M_MSEG_WWE-->     Goods Receipt for Purchase Order: Plant
M_MSEG_WWF-->     Goods Receipt for Production Order: Plant
M_RAHM_BSA-->     Document Type in Outline Agreement
M_RAHM_EKG-->     Purchasing Group in Outline Agreement
M_RAHM_EKO-->     Purchasing Organization in Outline Agreement
M_RAHM_WRK-->     Plant in Outline Agreement
Q_TCODE     QM -->         Transaction Authorization
S_ADMI_FCD-->     System Authorizations
S_ALV_LAYO-->     ALV Standard Layout
S_BDS_DS-->     BC-SRV-KPR-BDS: Authorizations for Document Set
S_BTCH_ADM-->     Background Processing: Background Administrator
S_BTCH_JOB-->     Background Processing: Operations on Background Jobs
S_CTS_ADMI-->     Administration Functions in Change and Transport System
S_DATASET-->     Authorization for file access
S_DEVELOP-->     ABAP Workbench
S_DOKU_AUT-->     SE61 Documentation Maintenance Authorization
S_GUI-->                     Authorization for GUI activities
S_OC_DOC-->     SAPoffice: Authorization for an Activity with Documents
S_OC_ROLE-->     SAPoffice: Office User Attribute
S_OC_SEND-->     Authorization Object for Sending
S_PACKSTRU-->     Internal SAP Use: Package Structure
S_PRO_AUTH-->     IMG: New authorizations for projects
S_RFC-->                     Authorization Check for RFC Access
S_SCD0     -->                Change documents
S_SPO_DEV-->     Spool: Device authorizations
S_TABU_DIS-->     Table Maintenance (via standard tools such as SM30)
S_TCODE     -->                Transaction Code Check at Transaction Start
S_TRANSLAT-->     Translation environment authorization object
S_TRANSPRT-->     Transport Organizer
S_WFAR_OBJ-->     ArchiveLink: Authorizations for access to documents
V_LIKP_VST-->Delivery: Authorization for Shipping Points
V_VBAK_AAT-->Sales Document: Authorization for Sales Document Types
V_VBAK_VKO-->Sales Document: Authorization for Sales Areas

Have you executed a trace while a functional user executes the transaction code for the specific parameters? (i.e. document type). The trace will then show which objects are being checked; then look at the object documentation in txn Su21 to determine if there are any ways to restrict on the particular value; in some cases, if the authorization group field is being checked, additional configuration is needed in order to implement the security (Su21 will explain in detail for the particular object).

Document type with posting level 12 not being carryforward

Hi gurus,
We are now implementing SEM-BCS 6.0 in the BI 7.0 server.
We have a document type u201CMIu201D which properties are:
Posting level: 12
Balance check: 0 error when balance note equal to zero
Application: Other
Posting: Manual posting
Inversion: No automatic inversion
The problem is that when we execute the Balance Carryforward in the subsequent year this is the only document type that is not being carryforward.
Why is this happening?
Thanks for your help.
Best regards.

This is by design
http://help.sap.com/saphelp_erp60_sp/helpdata/en/0c/ab0240536fe369e10000000a155106/content.htm
"Data records for preparatory postings for consolidation group changes are neither translated nor carried forward."
I'll try an example...
Company A is sold from company 1 to company 2 in June (EoP)
For periods 0 - 6:
BCS reports company A's balance sheet under company 1
BCS reports company A's income statement under company 1
starting period 7
BCS reports company A's balance sheet under company 2
BCS reports company A's 0 - 6 income statement under company 1
BCS reports company A's 7 income statement under company 2
this is managed through the posting level 02 12 and 22 document types, as well as PL30 if using CoI.
Assuming the period of first consolidation and period of divestiture were set correctly in the groups for company 1 and company 2, BCS wants to read all 0 - 6 data under group 1 and all 7 + data under group 2. This is obviously incorrect from an accounting standpoint and the PCC postings correct that.
So BCS books a PL02/12/22 in group 1 to zero out the balance sheet. It then books another set of entries in group 2 to write up the entire balance sheet in the new group.
However, once you get to the end of the year and run your BCF, the entire balance sheet is now sitting in period 0. The system is able to report company A's balance sheet under group 2 withou the aid of the PCC documents. Therefore, the system does not roll these documents forward into the new year.
The PCC documents were only required because of the periodic nature of the BCS data storage vs. the LTD nature of the balance sheet for reporting. Once the full LTD balance is available in a single period, as is the case just after a BCF, the PCC documents are no longer required.
Anyway, hope that made some sense. If not, I'd encourange you to create an Excel sheet replicating how BCS stores the data in the cube, perfrom a divestiture, and see why the system is not carrying forward the documents. This is how I came to understand it.
Now, if you're doing something "non-standard" with the PL12, all bets are off
Good luck,
Chris

Quantity field not getting displayed for all document types

Hi,
I have made a configuration to include field Quantity(BSEG-MENGE) in the GL account line item display.When I ran the report for stock adjustment account(FAGLL03), only the following document types are showing quantity against them.
WI- Inventory document
WA-Goods Issue
WE---Not showing quantity against (WE- Goods Receipt)
Can any one please explain. I have seen the original document from FI document. The original document as well as FI document carries quantity.
Thanks
Aravind

Hi Aravind,
Check SAP notes 1063198 and 1117587.
FAGLL03 display quantity which is updated in FAGLFLEXA, BSEG is not
relevant in this case. This is clearly explained in the note 1063198.
The quantity posts through to FI on the 'goods receipt' items, but not on the
'invoice receipt' items.
In the FI normally the Quantity is not a 'real' important field, as it
is more related to the MM area.
But in the old 'Profit Center Accounting' and the old' Special Ledger'
the field has been important.
As the same logic of these areas to 'store' the Quantity is also used
in the NewG/L the field get only filled in the line, where it make
'sense' from our point of view, because only in the 'goods receipt'
lines a 'real' Quantity is posted to the system.
So as before in the PCA and SL, now also in the NewG/L the Quantity is
filled in the correct and important lines and postings.
In the BSEG ('old document segment table') the field is filled 'just'
as it is send to the FI, but this is not completely correct from the
business point of view.
This can also lead to issues with the reporting and summation to this
field. So with creating the new logic in the NewG/L the 'correct'
standard of the 'writing' for the Quantity has also been taken over.
So in the end, the update and display is correct according SAP standard behavior.
Actually,Quantities within G/L are never reliable,
because the purpose of FI is a view on the data according to amount
but not according to quantity.
In the FI normally the Quantity is not a 'real' important field, as it
is more related to the MM area.
I hope I could be of assistance.
Regards,
Fernando

SAP table for customer account balances by document currency

Hi experts,
We have a requirement to produce a monthly customer statement by customer currency or customer's document currency. Example is that the company code local currency is USD and the customer currency is EUR. The customer will be allowed to carry over a balance to next period under a certain threshold so there will be a carry over beginning balance from the previous period which needs to appear on the statement. Transaction FD10N only displays customers balances in the local or company code currency which is USD in this example.
Question: Does anyone know if there is an SAP table that stores period beginning balances by customer account currency or customer's document currency?
We have not been able to find one and want to get additional input prior to building our own custom table.
Many thanks in advance for your assistance.
Regards,
NormaF

Hi:
Make use of BAPI_AR_ACC_GETKEYDATEBALANCE to calculate customer opening balance. You need to develop Z report using table BSID and BSAD other SD related tables . There is not SAP standard report that shows the customer opening balance as carried forward from previous month.. You can make alteration for for showing balances in document currency.
Regards

Retrive document types from BKPF / BSEG

Hi guys,
I need to extract records with the following document types from BKPF
- RE (Invoice Gross with PO)
- RA (Sub.cred.memo stlmt with PO)
- KR (Vendor Invoice without PO)
- KG (Vendor credit memo without PO)
- ER (E-Payment)
- TE (Travel & expense)
- KD (Down payment)
and then for these records the BSEG entries with these posting keys
- 31 (link to Payment via clearing document)
- 40 (debit entry, for non-PO voucher)
- 50 (credit entry, for non-PO voucher)
- 86 (GR/IR Debit, link to PO Line, positive)
- 96 (GR/IR Credit, link to PO Line, negative)
Extractor 0fi_gl_4 does not provide me wtih all these doc types, only a subset.
0fi_ap_4 is not an option for me, because in the data warehouse I need to link the bkpf/bseg records to the PO (ekko/ekpo), while we have no po reference in bsik/bsik that are read by 0fi_ap_4.
Is there a way to extend the fi_gl_4 so it contains the doc types I need?
Or do you know another way of retrieving bseg records of specific types?
Regards,
Arjen

ok,
I have checked again and if you didn't change the business content, both fields BLART (doctype) and BSCHL (key) are extracted; how was your delta init done? with selections? Did you apply some specific TRules or URules? Check you PSA for a record you are missing and simulate the update in order to see what's going on.
As I said, I got everything in my ODS.
you can also check this in R/3; Tx RSA3 with a comp_code and a fiscal period selection...
hope this helps
Olivier.
Message was edited by:
        Olivier Cora

Logic in Creation of Document Types

Good Morning Folks-
Is there documentation on when to create a new document type? I am on an AR project and I have a client that has (in my opinion) duplicate document types. For example, they have 2 document types for incoming payments and they are different because cash comes via lockbox(FLB2) and the other comes from a wire. I have 4 document types to identify invoices and they are different because they come from the legacy system or created in SAP, etc. They have a document type for credit memos and typically I have seen it is the same as an invoice but differentiated by posting key. For credit memo, would be posting key 11.
I am trying to find some documentation that gives advice and warnings about this. I have worked with 9 US A/R projects and at most had to be concerned with was only 4 document types. I know what the definition of a document type is but they think it is to have them by source. I see warning flags here. I don't even know how to create clearing rules because it is so complex. In addition, they are unable to balance from their legacy system to SAP.
Points promised

Hi,
This looks to be a Business Process question or as per the requirements of the client. You can find documentation on document types and how to configure, but not on how many document types to be set up. This purely depends upon Business practice adopted by the client.
If a client has moved from a legacy system to SAP, the document types used in legacy system also influences this decision. There will be some reluctance to reduce or increase number of document types vis a vis legacy system.
There should be too many or too less number of document types. Basically, document types will be helpful for reporting and analytical decision making.
Thanks
Murali.

PO Document type and ERS default cchecked

Hi Guys
Need a bit of help here with an issue
My requirement --
When a Purchase order with specific document type is created for One time vendors the ERS check box should be ticked default in the PO Line item details in the invoice tab . Is there a user exit to full fill this requirement .
Looking forward for an answer.

Following are necessary customizings and preconditions for using the Invoicing Plan functionality in SAP -
1) You must maintain the settings in Customizing for purchasing (for example, invoicing plan type, date categories, date descriptions, and date sequence proposals). The related path is IMG ---> Material Management ---> Purchasing ---> Purchase Order ---> Invoicing Plan ......
2) The Purchasing document with FO Document Type (Framework Order) must be used. This document type requires that a validity period be entered in the PO header. This specification is adopted in the invoicing plan, provided that this has been predefined in Customizing for the relevant invoicing plan type.
3) The purchase order item must have an account assignment.
4) The Logistics Invoice Verification must be used.
5) The vendor must have agreed to use the automatic invoice creation facility (since we will use automatic settlement to create the invoice). In this case, the 'AutoEvalGRSetmtDel.' indicator must be flagged in the vendor master record.
Furthermore, once Purchase Order is created with order type FO, ensure that the indicators for GR/IR control have been set correctly on the item detail screen. The Goods Receipt indicator may only be set in combination with the Goods Receipt Non-Valuated indicator. The Invoice indicator must be set. For the automatic creation of invoices, the ERS (Evaluated Receipt Settlement) indicator must be also set. A further prerequisite for automatic settlement is that a tax code must be entered in the purchase order.

SAP Best Practice for Document Type./Item category/Acc assignment cat.

What is the Best Practice for the document Type & Item category
I want to use NB - Item category - B & K ( Blanket PO) , D ( Service) and T( Text) .
Is sap recommends to use FO Only for the Blanket Purchase Order.
We want to use service contract (with / without service entry sheet) for all our services.
We want to buy asset for our office equipments .
Which is the best one to use NB or FO ?
Please give me any OSS notes or reference for this
Thanks
Nick

Thank you very much for your response.
I hope I can provide some clarity on how the accounting needs to be handle per FERC Regulations. The G/L balance on the utility that is selling the assets will be in the following accounts (standard accounts across all FERC Regulated Utilities):
101 - Acquisition Value for the assets
108 - Accumulated Depreciation Value for the assets
For an example, there is Debit $60,000,000 in FERC Account 101 and a credit $30,000,000 in FERC Account 108. When the purchase occurs, the net book value for the asset will be on our G/L in FERC Account 102. Once we have FERC Approval to acquire the plant assets, we will need to enter the Acquisition Value and associated Accumulated Depreciation onto our G/L to FERC Account 101 and FERC Account 108 respectively with an offset to FERC Account 102.
The method that I came up with is to purchase the NBV of the assets to a clearing account. I then set up account assignments that will track the Acquisition Value and respective Accumulated Depreciation for each asset that is being purchased. I load the respective asset values using t-code AS91 and then make an entry to the 2 respective accounts with the offset against the clearing account using t-code OASV. Once my company receives FERC approval, I will transfer the asset to new assets that has the account assignments for FERC Account 101 and FERC Account 108 using t-code ABUMN or FB01.

PCA balancing - A0 document type in period 14

Similar Messages

Maybe you are looking for