ERROR IN PSA MAINTENANCE SCREEN

Hi all,
I loaded data successfully and went into the PSA. I then went into the PSA maintainence screen and the very first line in the STATUS column i see a triangle with a ! . It says that:
"Fiscal Year Variant Z1 not expected"
This error is causing the data to not go into the cube.
What is this error about and how can i fix it?
Thanks
David

Normally the cubes are partitioned based on the fiscal year variant as K1, K4 or any fiscal year variant that is specific to the client they have defined.
Goto RSA1 and search your cube go to display and right click on fiscal year variant infoobject and choose display properties-->under constant value you shd see a value which is specific for that client.
You need to restrict this value in your infopackage load for that value only.

Similar Messages

Material Master - Error M3 826 Maintenance status of field ... to screen

Hi Experts of the Material Master,
I am getting the error M3 826 "Maintenance status of field MARA-BEHVO does not correspond to status of screen K" when all screens are selected in the Create Material Master transaction.
Here is my situation: I have added the fields MARA-BEHVO and MARA-TEMPB both of status L (Storage) to a screen called "Phys. Characteristics", which has status K (Basic data).
This produces the error message above in standard SAP. I didn't want to change the customizing of the screen to allow L, because this screen is also used by other material types.
I had to copy the screen MGD1 2701 (Phys. Characteristics) to my custom program for Material Master screens anyhow, as the number of fields and their descriptions had to be adjusted.
The program was created using the activity "Create Program for User Subscreens" in SPRO.
in the coding of ZMGD1 screen 2701 I have added this code behind the standard module FELDAUSWAHL to manipulate the standard logic that would blend out L fields on a K screen.
LOOP AT SCREEN.
*   Material Type
    IF mara-mtart = 'ZPNT'.
*     Screen-Names of the 3 fields
      IF screen-name = 'MARA-TEMPB' OR
         screen-name = 'MARA-BEHVO'.
        screen-active      = 1.
        screen-invisible   = 0.
        screen-output      = 1.
*       Change or Create transaction
        IF sy-tcode = 'JP27' OR sy-tcode = 'JP28'.
          screen-input       = 1.
          screen-required    = 1.
        ENDIF. "transaction code JP27 or JP28
        MODIFY SCREEN.
      ENDIF. "screen-name
    ENDIF. "Material Type ZPNT
ENDLOOP.
It all works fine when only a number of screens (but including the modified) screens are selected for creation.
But it fails with the message above on the modified screen when all screens are selected.
Any ideas?
Ralf

from the message, it appears that ZZKUNNR is a custom field attached to your MARA table. So, it is your System specific. I don't see ZZKUNNR available in MARA. If you look at the transaction code OMT3B (configuration for material master data screens), you can find K - Basic Data Screen in Maintenance Status field.
You may look in this area to fix your issue. Because yours is a custom field, its tough to analyse further.
Reward points, if it helps!
Regards

Issuing an Error in Table Maintenance Event

Hi,
How can I issue an error in the table maintenance event without exiting the screen.
When an event is triggered (Before Save), it will perform a check in the data changed or created. It will issue an error when the changes are not correct. But when I press enter or click on the check button, it will exit the table maintenance screen.
What do I have to do in order to issue an error but will still go back to the table maintenance view.
Making the message as information or type I, will not work because it will still save.

Hi,
I came to the same problem, maybe this will help someone.
You can move check into view cluster event.
1. load the view
     PERFORM vcl_set_table_access_for_obj
          USING 'view'
          CHANGING error_flag.
2. assing to structure
     LOOP AT <vcl_total> INTO ls_view
3. perform check, set VCL_STOP which will stop saving and will display message
     VCL_STOP = 'X'.
     MESSAGE ....

Throwing error msg in selection screen

Hi all,
I want to throw one error message in selection screen .
This message is of more than 1000 chars. and i want to show these 1000 chars in a pop up window and when i press 'TICK' mark, it should stay only in the selection screen . It should not go to the output screen and it should not leave the transaction either..
Can anyone help me in this by providing the coding for this..
Regards,
Shanthi

Hi Shanthi,
Your requirement is fulfilled by standard SAP message processing. Through message maintenance (TCode SE91), you define a message with a long text.
Let us say the message class is ZSHANTHI and the message number is 025. Besides the message short text you defined say 'Something wrong with &. Refer Long Text', un-check the checkk-box 'Self Explanatory', choose this message number and click on 'Long Text' button on the application toolbar. You will get long text editor and you can compose your 1000 lines or even 1000 pages story there.
Now let us see what you need to do in the report program. Your requirement is 'Issue the error message. When user hits Tick, display long text in a modal window and later stay in the same selection screen'.
You just issue this message in AT SELECTION-SCREEN event as:
MESSAGE e025(ZSHANTHI) WITH 'requirement'.
The error message will display on the status bar and when user hits the message X button, the long text with your story will appear in a modal box and still selection screen stays.
If your client is adamant in having only 'Tick' mark (this sucks me), you can add DISPLAY LIKE 'S' addition to the above message statement. But this addition works only 4.7 upwards.
If you want to issue this error message in list processing events like START-OF-SELECTION, then, you need to issue the following statements:
MESSAGE s025(ZSHANTHI) WITH 'still weird requirement'.
Note the message type 'S' above.
LEAVE LIST-PROCESSING.
Hope this helps.
Regards
Suresh Radhakrishnan

How to change width of table maintenance screen in sm30

Hi,
I want to change the width of table maintenance screen in sm30 of a view. I am trying to change it through screen painter.
But its giving me error - screen or window limit reached. I want to increase the widht to show all the fields at once.
Is there any way for this?
Also, earlier in table maintenance generator of view, there was one step selected. I changed it to two steps and re-generated the TMG. But again Its showing only one screen in sm30.
Kindly tell me which step I have missed out.
Regards,
Seema Naharia

I guess the links below should help in your problem ..
http://www.saptechies.com/how-to-create-table-maintenance-generator/
Window size on SM30
If these do not please tell ..
Regards,
Manthan

Errors In PSA

Hi All
I am getting errors in PSA when Loading Master data
The errors are
1.ZACTPAR : Data record 77 ('000300000089 '):
Version 'Rebserve FM ' is not valid RSDMD 194
2.Value 'Rebserve FM ' for characteristic ZACTPAR
contains invalid characters RRSV 7
Can some body tell me what the prob is and how to solve it
Regards
Vasu

Hi Vasu
You can see this erroraneous value in PSA maintenance RSA1-> PSA and here select your requst and edit PSA.
Please check if the value 'Rebserve FM' is not valid value for your characteristic ZACTPAR. You can get change this value in PSA and then re-load. Prior to this discuss this with R/3 people and get confirmation of this value.
If this issue is with invalid characters (hash like wired characters) then refer to this thread
Re: Regarding Special Characters
Hope this helps
Regards
Pradip

Removal of error from psa

hi friends
can any one tell me how can we remove an error from psa
thanks in advance
with regards
kalyan

Hi,
   Using the Error Handling function on the Update Parameters tab page in the scheduler, you can control the behavior of the BI system if data records with errors occur in the data flow with 3.x objects (use of transfer and update rules) when you are loading data using the PSA.
The system checks for data records with errors:
      in the transfer rules
      in the update rules
      when data is updated to the master data tables, text tables, or hierarchy tables
      when data is updated to the InfoCube
      when checking for referential integrity within an InfoObject against the master data tables or DataStore objects on the communication structure level.
Features
Incorrect records arising in transfer rules, update rules, when updating to a data target, or when checking for referential integrity, are highlighted and returned to the error handler. The error handler locates the original PSA records and writes the corresponding log. This function is not yet available for updating to DataStore objects.
Using the Error Handling function on the Update Parameters tab page in the scheduler, you can control how the system responds to incorrect data records.
Activities
       1.      Define how the system should react to incorrect data records
a.       No update, no reporting (default)
If errors occur, the system terminates the update of the entire data package. The request is not released for reporting. However, the system continues to check the records.
b.       Update valid records, no reporting (request red)
This option allows you to update valid data. This data is only released for reporting after the administrator checks the incorrect records that have not been updated and manually releases the request (using a QM action, that is, by setting the Overall status on the Status tab page in the monitor).
c.       Update valid records, reporting possible
Valid records can be reported immediately. Automatic follow-up actions, such as adjusting the aggregates, are also carried out.
With option a), the incorrect records are marked in red in the PSA maintenance. You can display the relevant error messages amodally, edit the records, and update the request manually. If it was not possible to write to the PSA (hierarchy or transfer method IDoc), an application log is written instead.
With options b) and c), a new request that is only updated to the PSA is formed from the incorrect records. Here you can edit the records of the new request in the PSA and start the update manually.
If errors arise when an InfoCube is updated, new requests are generated for incorrect records for each InfoCube combination. Among these requests, the incorrect records are updated to the PSA. These new requests have entered as data targets the InfoCubes for which there were incorrect records. If, for example, a record was updated to two InfoCubes by mistake, a request is generated for this record that contains both InfoCubes as data targets. In the PSA tree, the requests appear as successfully updated in the PSA. These new requests can then be triggered again for updating to the InfoCubes.
       2.      Specify the maximum number of incorrect data records that are allowed before the system terminates the load process. In the PSA, you can display the errors that have arisen up to that point. If you do not specify the maximum number of incorrect records after which termination should occur, the handling of incorrect data records is inactive and the update terminates after the first error.
       3.      Define how the BI system should react if the number of data records received by the BI system is not the same as the number of data records updated in BI.
A difference between the number of received and updated records can occur:
         in the transfer rules
         in the update rules
         when updating
Records are sorted, aggregated, or added.
If you set the No Aggregation Permitted indicator, the request is deemed incorrect if the number of received records is not the same as the number of updated records.
Regardless of this indicator, an error occurs if the number of selected records is not the same as the number of records received in the BI system.
Result
The monitor directs the user to the relevant error case and enables a direct navigation into the PSA or the respective error request.
If you want to continue processing the incorrect data records in a program that you have written yourself, you can use the method GET_ERRORS of class CL_RSSM_ERROR_HANDLER. The use of this method is documented in the RS_ERRORLOG_EXAMPLE.
To perform complex checks on data records, or to carry out specific changes to data records regularly, you can use delivered function modules (PSA-APIs) to program against a PSA table.
If you want to execute data validation with program support, select Tools ® ABAP Workbench ® Development ® ABAP Editor and create a program.
If you use transfer routines or update routines it may be necessary to read data in the PSA table afterwards.
Employee bonuses are loaded into an InfoCube and sales figures for employees are loaded into a PSA table. If an employees bonus is to be calculated in a routine in the transformation, in accordance with his/her sales, the sales must be read from the PSA table.
       1.      Call up the function module RSSM_API_REQUEST_GET to get a list of requests with request ID for a particular InfoSource of a particular type. You have the option of restricting request output using a time restriction and/or the transfer method.
You must know the request ID, as the request ID is the key that makes managing data records in the PSA possible.
       2.      With the request information received so far, and with the help of the function module, you can
         read RSAR_ODS_API_GET data records from the PSA table
         write RSAR_ODS_API_PUT changed data records in the PSA table.
RSAR_ODS_API_GET
You can call up the function module RSAR_ODS_API_GET with the list of request IDs given by the function module RSSM_API_REQUEST_GET. The function module RSAR_ODS_API_GET no longer recognizes InfoSources on the interface, rather it recognizes the request IDs instead. With the parameter I_T_SELECTIONS, you can restrict reading data records in the PSA table with reference to the fields of the transfer structure. In your program, the selections are filled and transferred to the parameter I_T_SELECTIONS.
The import parameter causes the function module to output the data records in the parameter E_T_DATA. Data output is unstructured, since the function module RSAR_ODS_API_GET works generically, and therefore does not recognize the specific structure of the PSA. You can find information on the field in the PSA table using the parameter E_T_RSFIELDTXT.
RSAR_ODS_API_PUT
After merging or checking and subsequently changing the data, you can write the altered data records into the PSA table with the function module RSAR_ODS_API_PUT. To be able to write request data into the table with the help of this function module, you have to enter the corresponding request ID. The parameter E_T_DATA contains the changed data records.

Creating Customized Table and Modify Table Maintenance Screen

Hi,
I have already created customized table and generate the table maintenance screen, however i encountered 1 problem which is i cannot add new PAI and PBO module in the flow logic. Every time i wanna add new module, i will be getting error message saying that my user currently editing the screen. Any suggestion ?
Thanks.
Jon

Hi <b>Jonathan</b>,
Please close all the windows and relogin
For making PAI and PBO modules, Please activate all the Table and its maintainence view.
Now first make emptu file with <main filename>_PAI and <main filename>_PBO save and activate them.
Now put the logic in them and then activate now call these in the main prog.. it should work...
While activation all the sub program modules should be activated already... i suggest select all the prog and sub progs and activate them all at once...so the system automatically takes care of inner activations first...
If u have some more quereies... please feel free to contact me...
Regards,,
<b>Abhishek</b>

While loading master data into PSA, the eorror is 'Error from PSA"

Hi All,
While loading master data into PSA, the eorror is 'Error from PSA"
Could you anybody please help in this reagard.
Thanx,
Sridhar.

Hi rakesh,
May be IDOCs not processed completely,
Idoc Problem, Either wait till time out & process Idoc from detail monitor screen, or go to BD87 & process Idoc with status = YELLOW ( be careful while processing IDOCS from BD87, choose only relevant Idocs
Cheers
Raj

Error while writting a screen in report

Hello Friends,
                        I am running a report while executing i am getting error Error when writing a screen,
If anyone have useful answer please replay.
Thanking
Shrikant

Hello ,
While running program i am getting following dump error.
Short text
    Error when writing a screen.
What happened?
    Error in the SAP kernel.
The current ABAP "ZHRM_DEVIATION_ALL" program had to be terminated because the
    ABAP processor detected an internal system error.
Thanks
Shrikant

Itunes wont launch, no error message, no blue screens, just wont open

itunes wont launch, i get no error message, no blue screen, it just wont open. I've tried to delete and reinstall, but once i close itunes i still have same issue. it wont open again.

I have same problem on my XP lap top and Windows 7 PC. Apple have been investigating this problem for me for a week now without success so far. Understand it 's ongoing with other customers as well.
It is caused by an bit of program called APSDaemon supplied by Apple in latest i-Tunes. Your quick fix to enable you to open i-Tunes again is as follows:- open Task Manager (right click bottom toolbar), click on Task Manager, select Processes. Find APSDaemon, highlight and press END PROCESS. I-tunes will now re-open ok. You have to repeat this every time you want i-Tunes re-opened until you switchoff or restart.
A pain I know, but lets you keep going until Apple repair and release an update for i-Tunes

How to give error message for the screen element text field when wrong i/p

How to give error message for the screen element text field when wrong i/p
when wrong input given
eg.
I have a text box with SBOOK-CARRID
so when user give wrong entry in text box i.e LG
then I should give some error stating that the the input is invalid or not available ,
now it showing the error of standard messages,
i want manual message to be displayed when error comes.
Thank you,
Regards,
Jagrut Bharatkumar Shukla

Hi all,
Thank you for your valuable reply,
but the thing is that its a screen field,
i.e text box not a selection screen
i created in screen layout
with name sbook-carrid
now i want to get error message display if wrong i/p is given
thank you.
Regards,
Jagrut bharatkumar Shukla,

Error Message in selection screen Status bar is getting truncated

Hi Guys,
Error Message in selection screen Staus bar is getting truncated (full message is not getting displayed).... can anybody tell me how to reslove this

Hi
Maimum we can give the error message length is 50 char. If you give more than that it will get truncated.
What you can do this split 50 and 50 like that you can give 200 chnars.
Data : Text1 type char50
Text2 type char50
If sy-surc ne 0.
Message Text1 Text2 TYPE "E'' or 'S'
endif.

Error in PSA with special characters

Hello,
I'm having a problem with sprecial characters in PRD system.
This happen with standard extractor for Confirmations in SRM module, 0BBP_TD_CONF_1.
I have 5 records with error in PSA. The field that have the error is 0bbp_delref and it has the text: GUIA ENTREGA Nº2.
The error message says that field OBBP_DELREF has special characters that are not supported by BW.
The field is char 16 and in spro I have the characters:
QWERTYUIOPASDFGHJKLÇªNºZXCVBM/~^´`* '()"#$%&!?.-0123456789Â«»<>
In QUA, I created confirmations with this text and it worked fine and the characters in SPRO are the same.
Any idea?
Thanks and best regards,
Maria

Hi Maria,
There will be no issue with update rules as the issue is with Data..
ALL_CAPITAL should resolve your issue, .otherwise try individually executing those spl characters in RSKC..
have you tried in SPRO...
Check in this table RSALLOWEDCHAR in SE11 and find what all characters allowed(permitted) in PRD system...
please go through the above mentioned blog once
Thanks,
Sudhakar.

"****Error from PSA****" error message when loading InfoCube

Hi all,
I am getting the following error message when loading transaction data to an InfoCube.
***Error from PSA***
This is not MD or Hierarchies (like previous messages in the forum)
Please advise.
Thanks,
Miki

Hi Miki,
Before just loading data into the infocube. Catchup PSA table and see the data into it.
Then u may find the solution.
But as ronald said this shouldnot be the complete error statement.
bye.

ERROR IN PSA MAINTENANCE SCREEN

Similar Messages

Maybe you are looking for