How to test the object is base 64 encoded or not.

Hi,
MimeUtility is which I am using for base 64 encoding of object.
but while decoding I want to test whether the object is base 64 encoded and then only I want to decode it. actually while encoding I will be encoding it based on some criteria. If that criteria is satisfied then I will be encoding the object else I will not do so but I cant test it same way again so I have to explicitly test whether its encoded at base 64 encoding then only decode it.
Sorry it seems to a long story :)
Thanks in advance.

If that criteria is satisfied then I will be encoding the object else I will not do soSo, you're not saying what that criteria is, but you're asking if there is some way (and I suspect asking for some way) of determining, after the fact, whether that criteria was met.
Depending on the criteria, and the method of encoding, I would have thought it quite possible for some object which was not encoded to be in every respect identical to the encoding of some other object. In this case it would not be possible to determine whether some arbitrary object was the result of an encoding.
But then, as already pointed out, you know if you encoded something or not.

Similar Messages

How to migrate the Objects from 3.1c to BI7

Hi,
We are in Functional Upgradation.
How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
Please help me to doing this....
regards,
anil

BW Upgrade tasks (BW 3.1C to BI 7.0)
Prepare Phase:
Task     How-To     Who
Review BI 7.0 feature lists     Review BI 7.0 feature lists for possible inclusion in developments.     Basis/BW
Obtain the BI 7.0 upgrade guide     Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
     Basis/BW
Review all upgrade SAP notes     In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
     BI 7.0 Upgrade notes
     SAP Web Application Server 6.40 upgrade notes
     OS and DB specific upgrade notes
     SAP BW Add-on upgrade notes
(e.g. SAP SEM, ST-PI, etc)
     Plug-In upgrade SAP notes
     Other notes identified in above notes and/or upgrade guides.
     Basis/BW
Check DB and OS requirements for the target SAP BW release     Check DB version/patch level and OS version/patch level required for upgrade
     First check the most current information from the SAP BW homepage http://Service.sap.com/BW -> <SAP BW release> -> Availability
     Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
     Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
     Basis
Check SAP BW Add-on upgrade requirements     Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
     SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
     WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
     Basis
Check SAP BW upgrade requirements          Minimum Support Package and kernel levels for upgrade
     SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
     Source system Plug-In requirements     Basis
Check compatibility requirements with 3rd party software          3rd Party Reporting tools (example: Crystal)
     ETL Tools (example: Ascential, DataStage, etc)
     Scheduling tools (example. Control-M, Maestro, etc)
     Monitoring tools (example: HP OpenView, Patrol, etc)
     Other OS or DB related tools     Basis
Check new component requirements for BI 7.0          If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
The IGS chart migration will also be required after the SAP BW web report conversion.
     If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
     If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0. (ArcView 8.2?).
     If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides -> SAP NetWeaver).
     Basis
Test and distribute new SAP BW Frontend
          Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
     A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
     After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
     Basis
Alpha Conversion:
Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool)      Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
Transaction RSMDCNVEXIT
Check the system status:
     u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
     u201CNo Check yet/Inconsistent Internal Vales existu201D:
The Alpha converter check has not been executed.
     u201CCharacteristics have Inconsistent Internal Valuesu201D:
The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
     BW
Upgrade SAP Note updates     Check for newer versions of your SAP notes for the Upgrade.
Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
     Basis/BW
Confirm SAP BW support package, kernel and DB/OS configuration     Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
     Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
     Basis
Alignment of SAP BW objects within your SAP BW system landscape     Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
     This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
     Basis/BW
Confirm all developments are deployed.     Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
     In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
For SAP BW developments not already collected in the transport collector, a decision must be made:
Deploy the developments or wait until the upgrade has completed to deploy.
o     Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
o     Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
     In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
     BW
Implement BI 7.0 Business Explorer Frontend     Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
     Basis/BW
Pre-upgrade Process:
Download required BI 7.0 support package Stack for inclusion in the upgrade     Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
     There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
     It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
     BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
     You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
     Basis
Apply latest Support Package tool patch     Apply latest SPAM patch before executing PREPARE     Basis
Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency     Check Database consistency
     Transaction DB02:
o     Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
o     Check missing database objects (indices, tables, etc)
o     Missing indices may identify erred data loads or process problems
Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
Note: check for running data loads before executing a repair!
o     Check DDIC/DB consistency
     Verify database objects and consistency
(e.g. SAPDBA check for offline data files)
     BW
Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
     This reduces the numbers of database objects that need to be copied during the upgrade.
     Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
     BW
Validate your SAP BW Objects for correctness prior to your upgrade     Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
Note: this test should be repeatable so you can re-validate after the upgrade!
     Ensure that any inconsistencies are identified and corrected
     RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
     Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
     BW
Ensure DB Statistics are up to date prior to the upgrade          Check DB statistics for all tables.
Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
     Check DB statistics for missing Indexes for InfoCubes and Aggregates
o     User transaction RSRV to check      BW
Check SAP BW Support Package status     Check the status of all support packages (via transaction SPAM)
     Ensure the Support Package queue is empty
     Confirm all applied Support Packages     Basis
Check all u2018Repairsu2019     Check for unreleased repair transports
     Release all unreleased transports
In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
     Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
     BW
Check InfoObject status          Check for revised (modified) InfoObjects that have not been activated.
All InfoObjects should be active or saved (not activate):
o     Check all inactive InfoObjects:
Transaction RSD1 (Edit InfoObjects),
click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
Modified InfoObjects are denoted by yellow triangles!
o     Determine if revision should be activated or removed.
     'Reorgu2019 or u2018Repairu2019 all InfoObjects
This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
     Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
     BW
All ODS data loads must be activated.          Activate all inactivated ODS Object requests.
All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
o     Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
     BW
All Transfer and Update rules should be active          Check for inactive Update and Transfer Rules
o     All update rules and transfer rules should be active or deleted.
o     Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure.     BW
All InfoCubes should be active          Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
o     All InfoCubes should be activated or deleted.
o     Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
     BW
All Web Report objects should be consistent prior the upgrade.          Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
o     For Original release SAP BW 3.x:
A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
Please see SAP note 484519 for details.
     BW
Backup your system before starting PREPARE     Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
     Database admin
Address any instructions/errors generated by PREPARE          Address any issues listed in log files Checks. Log generated by PREPARE.
o     Repeat PREPARE until all checks are successful.     Basis
Complete any Logistic V3 data extractions and suspend V3 collection processes          Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
o     The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
     Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
     BW
Complete any data mart data extractions and suspend any data mart extractors          Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
o     The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
     Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
     BW
Check that your customer defined data class definitions conform to SAP standards          Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
o     Check your data class definitions as detailed in SAP Notes 46272 and 500252.
o     Incorrect data classes could create activation errors during the upgrade.
     BW
Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
     This reduces the numbers of database objects that need to be copied during the upgrade.
     Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
     Basis/BW
Backups!     Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
     Database Admin
Before Execution:
All SAP BW administration tasks should have ceased          Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
     Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
- timing depends on the type of upgrade selected
     Basis/Admin
Remove unnecessary SAP BW temporary database objects     Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
- timing depends on the type of upgrade selected
     BW
Check system parameters     Check OS, DB, and Instance profile parameters.
     Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
     Check for any DB specific parameters for BI 7.0
     Check for any new OS parameters     Basis
Check Database archiving mode     Turn database archive log mode back on if it was disabled during the upgrade!
     Database Admin
After Execution:
Check the systemu2019s installation consistency     Execute Transaction SICK to check installation consistency
     BW
Check the system logs     Perform a technical systems check.
     Example: Check system and all dispatcher logs (inc. ICM logs)
     Basis
Apply latest executable binaries     Apply the latest 6.40 Basis Kernel for all executables
     Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
     Basis
Review BI 7.0 Support Packages for follow-up actions.          Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
o      Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o     Follow any required instructions identified in the SAP Notes
     Basis
Apply latest patches          Apply the latest SPAM patch
     Apply any required support packages that were not bound into the upgrade.
     Basis
Apply additional BI 7.0 Support Packages
(if required)          SAP recommends that customer remain current on SAP Support Packages.
     Review SAP Notes for all SAP BW Support packages applied in previous task.
o      Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o     Follow any required instructions identified in the SAP Notes
     Basis
Resolve any modified SAP delivered Role issues      If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
     Review and implement SAP note 569128 as required     Basis
Configuring Information Broadcasting EP/KMC Connections
     If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
     Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
     Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
     For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
     Basis
Re-check SAP BW Object and consistency     Execute RSRV to check SAP BW Object consistency
     Repeat tests that we executed prior to the upgrade.
     Validate results      BW
Check InfoCube views for consistency     Check consistency of InfoCube fact table views
     It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
     BW
Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks          If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
     The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
     It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
o     Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
     Check that all other Source Systems are active.
o     Activate as required.     Basis/BW
Check SAP BW Personalization is implemented     (SAP BW 2.X upgrades will have performed this in the previous task).
Validate that personalization has been activated in your SAP BW system.
Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
     Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
     To activate highlighted Personalization, click Execute.     BW
For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert ODS secondary indexes to new standard     For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
     Re-create all indexes in the ODS Object definition screen in transaction RSA1.
     ODS indexes must conform to the new naming convention
     BW
Converting IGS chart settings
     Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
     Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
o      Test via transaction RSRT
     Execute the conversion process as directed the BI 7.0 upgrade guide.
     Note: This step is required for all BI 7.0 upgrades     Basis
Backup your SAP BW system     Perform a full database backup (including the File system)
Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
     Database Admin

How to UnLock the object in Integration Repository of XI.

Hi Experts, when i try to edit the object in IR, i am getting following message.
Object Message Mapping EmpResponce_MM | urn:pas.com/neh currently being edited by user 9SGRANDHI.
Note: it is saying my ID itself, i logged off and logged in, still its showing same mesage, how to unlock the object in Integration Repository of XI.
please help me out.
thanks
siva

Hi,
Go to Home page of XI,there u will have Administrator,select it and click on localobjects.There u will have IR and ID in that select lockoverview and remove ur lock.
this authorization will be given to basis guys check u have it or not.
Regards,
Phani
Reward points if helpful

How to test the connection between DSD backend and DSD connector

Dear all,
I am configuring the MDSD scenario .. and i want to insure that my customization is correct
How to test the connection between DSD Backend and DSD connector ??

Hi Viren,
The problem is:
We have a new BW system. The basis people asked me to check the connection between this BW system and the R/3. There is only one client for now(100). I have logged into 100 and tried executing RSA1 to check the connection, but it gave a message box saying "You can only work in Client 000". Then I have treid logging into 000(just to make sure) and tried executing RSA1. Even here I got a message saying "The SAP BW system must not be operated in client 000". Now, I am not sure of what is wrong in clien 100. I am not sure if I have to do some settings before I access RSA1 or any other BW transaction. Could you please help me in this.
Also, I just checked the RFC destinations in BW. There is a destination created for our R/3 and I have noticed that they have given a remote UserID and password for remote login. I tried to check the Remote UserID in SU01 but there is no userID with that name. Could this be a problem?
Thanks,
RPK.

How to see the object while moving on the artboard?

hello everyone;
maybe a silly question; how to see the object while moving on the artboard? i dont wanna see only the objects bounding box(outline of the object). i wanna see the object it self. thank you.

What have they gone and messed up now?
When I drag an object (with bounding boxes turned on), the object moves and the bounding box stays still until I stop dragging, upon which it snaps to the object’s new position.
If I don’t have bounding boxes turned on (as I usually work), the object moves when dragged.
If what Bedri says is right, they’ve gone and mended something that wasn’t busted.

How to get the object class field value in CDHDR table for vendor

hi
how to get the object class field value in CDHDR table for vendor

Try KRED/KRED_N as object class in CDHDR for Vendor.

How to test the payload in XI

Hi all,
could please explain how to test the payload in xi and with steps.
Thanks in advance,
Radhika

Hi Radhika,
You can test in three ways.
1.) In message mapping directly give the relevant data and then execute. Here you can test whether the mapping is correct or not.
2.) In Integrstion Directory after completing and activating the Configuration, in tool you can find the Test Configuration tab. There you can give the sender and receiver details along with payload. Here you can test whether the Configuration is correct or not.
3.) In RWB in COmponent monitoring. Select the Integration Engine Monitoring. Here give the sender and receiver details, Interface name, name space, Quality of service.
Now give user name and pass word.
Paste the payload from massage mapping and then press test tab. Here yoyu can directly send the message from XI server to the receiver system.
Ok,
Jeevan

How to test the rule if multiline container is passing to the task?

Hi Experts,
                  I am working on leave workflow. I have to get the approvers based on no of days of leave and leave type. I am getting these details in ITEMS_TAB internal table. I am passing this table to a rule. Now my problem is when I tried to simulate the rule I am not getting any input screen to enter the data.
ITEMS_TAB is an internal table type of   "PTREQ_ITEMS_WF_TAB_FLAT".
In the rule I have created a container by selecting the radiobutton "ABAP Dict. Data Type" and entered the above reference parameter is it right way?
Is it possible to test the rule independently if I use multiline container as import parameter in my rule? If so can anybody please tell me how to test the rule?
Thank You.
Srija.

Hi Pavan,
                 Thank you.
                 To copy the values I am not getting any input screen to input the values. I observed one thing that the type that I am referring in the Rule is a deep structure. Is this is the reason that I am not getting the input screen to enter the values?
I tested by creating aother rule by taking a field for that rule I am getting the input screen to simulate the Rule.
Can you please suggest if the rule will not work then what I have to do? without the rule how can I get the agents?
Thank you.
Srija

How to test the PMS/apprisal template

Hi experts,
We have completed the configuration of Apprisal templete.
With OOHAP_BASIC,PHAP_CATALOG_PA we have completed the process along with status and substatus,staus flow.
I struckup at this juncture.
How to test the entire process after the configuration.
Please advice.
Regards,
Sairam.

Hi Sairam,
To test the PMS process, please follow the below steps :
1. Go to PHAP_CREATE_PA and select your template. Enter the details for appraisee, appraiser, reviewer ( if applicable ) and also the start date and end date. Save the document.
2. Go to PHAP_ADMIN_PA and select the template/appraisee id in the appraisee column in the selection screen and execute. Select your appraisal document and then select from Menu- Appraisal Document->Change Status and select your initial status and sub status.
Now you can login to Portal/R3 with the user and start testing. The substatus will move automatically based on your workflow. Once you complete a particular status say 'In Planning' you need to manually change the status again from PHAP_ADMIN_PA to 'In Review'.
Get back to me in case of any queries.
Regards,
Sachin

How to test the modified script (Global Dunning)

Hi all,
I have a requirement in SAP Script.
I had modified Global Dunning Letter F150_DUNN_01 and the print program is SAPF150D2.
Transaction code is F150.
How to test the script and what is the access path for checking print preview of the modified form.
Do i need to configure anything before testing.
Rewards to all.
Thanks & Regards,
Aarthi.

Hi
Your functional consultant will help you to trigger the output of this dunning output
or search in SPRO tcode
o in the related tcode F150
<b>Reward points for useful Answers</b>
Regards
Anji

How to test the data

Hi,,
The below test data is for SD report which do the monthly batch transfer from Annexure to F-form
Can you please help me how to test the data? and prepare the unit test case.
1. Intra-plant movement of inventory between two plants with the same region Code - In India there are two plants in the state of Maharashtra.
Plant 8600 (Vendor 10999346) -> Plant 8601 - MM# 1003623 / 1013515 / 5214135 / 8788143
NB PO# 6500002231 / ZU PO 4600000500
2. Intra-plant movement of inventory from Plant 8650 - Goa to one Depot Plant
Plant 8613 (Vendor 10999359) -> Plant 8618 - MM# 1003623 / 1013515 / 5214135 / 8788143
NB PO# 6500002232 / ZU PO 4600000501
3. Intra-plant movement of inventory between two Parts plants.
Plant 8650 (Vendor 10999344) -> Plant 8601 - MM# 4908281 / 4908323 / 4908968 / 4922001
NB PO# 6500002233 / ZU PO 4600000502

Please go thorugh this ...
eCATT stands for extended Computer Aided Test Tool (eCATT) which is built is testing tool to test SAP system. By using testing tool we can test the entire business process, and we can also use this tool with a third party testing tool (I am not covering this topic). Execution of every test script ends with a log, which explains the results of the test script.
By using eCATT we can do following operations,
·        Test transactions, reports, and scenarios
·        Call BAPIs and function modules
·        Test remote systems
·        Check authorizations (user profiles)
·        Test updates (database, applications, GUI)
·        Test the effect of changes to customizing settings
·        Check system messages
For more information go to: eCATT::Extended Computer Aided Test Tool (sdn.com)
Here I am discussing fundamentals about eCATT in detail. You can find very good documentation in sdn.com.
To develop a test script in eCATT we need to follow the following steps,
1. Creating Test Scripts.
2. Creating Test Data Containers[16] .
3. Understanding System Data Containers[17] .
4. Executing Test Configurations.
There is a very good web blog on eCATT in sdn.com which explains eCATT with necessary screen shots. To read document click here Blog on eCATT in sdn.com
For details and the screenshots     please see the link
http://www.erpgenie.com/sap/ecatt/
Reward points if it is usefull ...
Girish

How to Test the individualmapping field and conditions...

Hi Frnds,
I done mapping from source to destination as per tech spec in my scenario based on some conditions
i used node functions also..
But my question is how to test the every mapping filed , condition is correct or not, what i used node function working properly or not...
Regards,
Raj

Hi
If you want to check mapping for individual mapping then in design go to test tab and put your data there and then come again on Design tab and click on any target field fro which you want to check mapping then right click on target field in mpping area and click on Display queue and check whether it is expected output for that particular field mapping.
Regards
Sami
Reward points if useful.

How to test the performed SAP SCRIPT

Hi friends can any one help for
how to test the performed SAP SCRIPT. What are the necessary codes or anything else for performing it

Praveen,
Can you be much clear with your query? What do you mean by performing? Do you mean how to execute it ?
Regards,
Vinod.

How to test the UDA or Attribute of an ancestor member

Hi everybody !I would like to know how to test the UDA or attribute (I can use both) of the ancestor (or the parent of the parent) of the current member please ?(the current member is on level 0 et the ancestor is on level 2).I tryed some syntax but any result :(Thanks very much for your help... JaspePS : Sorry for my "bad" english, i'm french...

You can try using this IF conditional statement:if (@count (skipnone, (@uda (dimName, myUDA) and @ancest (@currmbr (dimName), -2))) == 1)where:dimName is the dimension of the level 0 member you are testingmyUDA is the UDA you are testingWhat this does is it counts the number of members that meet two criteria. First, it must have the UDA you specify and, second, it must be an ancestor of the current member at a specified level.If the current member has a level 2 ancestor with the UDA, it should return one member.

How to test the adapters

hi
anybody can tell me how to test the adaptors?
regards,
krushi

Adapter Monitoring:
Steps:
1. Go to RWB.
2. In the Component Monitoring Select Adapter Engine
3. Select the Adapter Monitoring Tab.
Using this window u cam monitor
>> Installed and Started Adapters
>> Adapters with Error and
>> All the Adapters
Uses:
>>The name of the server on which the selected Adapter Engine was deployed. This can be a server cluster consisting of several nodes.
>>The namespace in which the adapters shipped by SAP are located. If you have created additional namespaces for your own developments or for third-party adapters, these are also displayed.
>>A list of all the adapters available for the selected Adapter Engine. Adapters that are not installed and started, or not registered with the Adapter Framework are GRAYED out. You can select all the other adapters to display additional information. i.e U can see all the Adapters.
If all the adapters are working then it will be displayed in GREEN.
If not then it will be displayed in RED.
If U are not using the adapters in ur scenarios then it will be GRAYED out.
Remember to set the thread to solved when you have received a solution
Use a Good Subject Line, One Question Per Posting - Award Points

How to test the object is base 64 encoded or not.

Similar Messages

Maybe you are looking for