SAP ABAP Message Class G9 (Joint-Venture-Archiving)

Basic Data

Hierarchy

☛ EA-FIN (Software Component) EA-FIN
   ⤷ CA-JVA (Application Component) Joint Venture und Production Sharing Accounting
     ⤷ GJV2 (Package) Joint Venture Development

Attributes

Message class	G9
Short Description	Joint-Venture-Archiving
Changed On	19990416
Last Changed At	155040

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	000	* ------------------- Joint-Venture-Archiving ------------------------- *		☐
2	001	* ------------------- Common Messages ------------------------- *		☐
3	002	Selection criteria 'Fiscal Year': From-Value is greater than To-Value		☐
4	003	Selection criteria 'Period': From-Value is greater than To-Value		☐
5	100	* ------------------------ JV_Pricing_Data ---------------------------- *		☐
6	101	Please correct the number for the package size (&) for JVKONV		☐
7	102	Please correct the number for the amount of documents to be read		☐
8	103	Internal error (Index): The name of the archiving object is missing		☐
9	104	Internal error (Index): There are no values for the archiving-index		☐
10	105	No archives have been selected yet nor a date interval has been selected		☐
11	106	Please specify the type of archives ('deleted or not deleted from DB')		☐
12	107	You do not have authorization to archive data in Joint Venture Accounting		☐
13	108	Please correct the number for the object-size per commit		☐
14	109	There exists already an index for the archive file &.		☐
15	110	There are no archives present with respect to the actual selections		☐
16	111	No archives have been chosen yet		☐
17	150	* -------------------------- JV_BILLING/JV_OBJECT --------------------- *		☐
18	151	There are no JVA-Billing ledgers present in the customizing		☐
19	152	No JV-Billing Ledgers with complete customizing expressions were found		☐
20	153	No 'company code-joint venture' combination exists for the selections		☐
21	154	No 'company code-joint venture-equity group' combination found		☐
22	155	There exist no versions in the customizing for the Billing ledgers		☐
23	156	No company codes exist in the customizing for the Billing ledgers		☐
24	157	No JVA Ledgers with complete customizing expressions were found		☐
25	158	There exist no versions in the customizing for the JVA ledgers		☐
26	159	No company codes exist in the customizing for the JVA ledgers		☐
27	160	No archiving possible: Bank account switching has to be executed first		☐
28	161	No archiving possible because of FI and bank account switching documents		☐
29	162	No archiving possible: FI document archiving has to executed first		☐
30	163	Please choose a Billing Ledger (4B, 4D)		☐
31	164	Checking JVA documents against bank account switching documents		☐
32	165	Checking JVA documents against existing FI-documents on the database		☐
33	166	Number of JVA documents excluded due to FI-documents: &		☐
34	167	Number of JVA documents excluded due to bank account switching: &		☐
35	168	Please enter a valid company code/controlling area combination	Space: object requires documentation	☐
36	169	No customized company code exist for the ledgers in question	Space: object requires documentation	☐
37	170	Not all desired ledgers could be considered	Space: object requires documentation	☐
38	171	An internal error occurred during the table check	Space: object requires documentation	☐
39	172	Enter a ledger summary table	Space: object requires documentation	☐
40	173	Summary table & does not exist in FI-SL.	Space: object requires documentation	☐
41	174	Summary table & has no corresponding actual line item table	Space: object requires documentation	☐
42	175	Summary table & has no corresponding planning line item table	Space: object requires documentation	☐
43	176	Only record type 1 or 3 is relevant to planning line items	Space: object requires documentation	☐
44	177	Enter record type 0 or 2	Space: object requires documentation	☐
45	178	Only record type 0 or 2 is relevant to actual line items	Space: object requires documentation	☐
46	179	No archive files or archiving runs selected	Space: object requires documentation	☐
47	180	The ledger-totals-table-name is missing	Space: object requires documentation	☐
48	181	Internal error occured during the archiving process (Archivingobject &)	Space: object requires documentation	☐
49	182	There are no JVA ledgers present in the customizing	Space: object requires documentation	☐
50	183	No JVA-table exists with respect to the selected ledgers	Space: object requires documentation	☐
51	184	Internal error occurred during archiving (archiving object &)	Space: object requires documentation	☐
52	185	No document restriction if accountwise archiving is selected !	Space: object requires documentation	☐
53	186	No account restriction if documentwise archiving is selected !	Space: object requires documentation	☐
54	187	Invalid selections: The variant used is not valid anymore !	Space: object requires documentation	☐
55	188	No document restriction if venture/partnerwise archiving is selected !	Space: object requires documentation	☐
56	250	* --------------------------JV_BANK_SW--------------------------------- *	Space: object requires documentation	☐
57	251	No data has been selected for the given select options	Space: object requires documentation	☐
58	252	The selections passed via the interface are not complete	Space: object requires documentation	☐
59	253	There are no readable files available for archiving object &	Space: object requires documentation	☐
60	254	Please specify an insert type ('array insert' or 'line insert').	Space: object requires documentation	☐
61	255	Please specify a structure name.	Space: object requires documentation	☐
62	256	Please specify only one desired commit type (db_commit or commit work).	Space: object requires documentation	☐
63	257	Please specify only one insert type (array insert or line insert)	Space: object requires documentation	☐
64	258	No archives have been selected	Space: object requires documentation	☐
65	300	*-----------------------JV process event--------------------------------*	Space: object requires documentation	☐
66	301	The fiscal year to be archived should be previous year or earlier	Space: object requires documentation	☐
67	302	Data cannot be archived in the current fiscal year	Space: object requires documentation	☐
68	303	There are open periods for company code & in the archiving period	Space: object requires documentation	☐
69	304	There are open periods in company code & for the period to be reloaded	Space: object requires documentation	☐
70	305	Do you really want to reload data in the actual fiscal year ?	Space: object requires documentation	☐

History

Last changed on/by	19990416	SAP
SAP Release Created in