Setting up your RMS Development Environment
Before you can write your first line of PL/SQL or query the item master, you need a properly configured workstation. Here is the step-by-step guide to setting up your Oracle RMS development environment.
Developing for Oracle RMS isn't quite like building a modern Node.js or React application. You won't be running npm install or spinning up a local Docker container for the whole application. RMS is simply too large.
Instead, development usually consists of connecting to a shared remote development database via an IDE.
1. Choosing your IDE
Since 90% of your work in RMS will be writing PL/SQL packages, analyzing data, and debugging data patches, your database IDE is your most critical tool.
- Oracle SQL Developer (Recommended): It's free, built by Oracle, and comes with excellent support for debugging PL/SQL, viewing query explain plans, and browsing schemas.
- PL/SQL Developer (Allround Automations): A very popular paid alternative favored by many veteran Oracle developers for its speed and rich PL/SQL editing features.
- Toad for Oracle: An enterprise-grade, heavy-duty client. It is extremely powerful but can be expensive and resource-intensive.
For this guide, we will assume you are using Oracle SQL Developer.
2. Connecting to the Database
You will need the following details from your DBA or Lead Developer to connect to the DEV environment:
- Hostname: e.g.,
dev-db.retail.yourcompany.internal - Port: Usually
1521 - Service Name or SID: e.g.,
RMSDEV - Username / Password: Your personal database credentials.
Do not use the RMS schema owner
In a properly secured environment, you should be assigned a personal database user (e.g., PPANDEY). You should not log in directly as RMS01 (the schema owner).
To query the tables without prefixing them with the schema name (e.g., writing SELECT * FROM ITEM_MASTER instead of SELECT * FROM RMS01.ITEM_MASTER), you will need to set your current schema.
3. Essential SQL Developer Settings
Out of the box, SQL Developer needs a few tweaks to make RMS development smooth.
Displaying DBMS_OUTPUT
RMS batch jobs and custom scripts frequently use DBMS_OUTPUT.PUT_LINE for debugging. By default, this output is hidden.
- Go to View -> DBMS Output.
- Click the green "+" icon in the new pane and select your database connection.
- This will ensure you see the log messages when you execute PL/SQL blocks.
Autotrace and Explain Plans
When querying tables with 50 million rows (like ITEM_LOC_SOH), you must ensure your queries are using indexes.
- Learn the shortcut key for Explain Plan (usually
F10). - Always run an Explain Plan before executing a new query on a massive transaction table.
4. Accessing the Server (PuTTY & WinSCP)
While your PL/SQL lives in the database, the Pro*C batch programs, shell scripts, and flat files (for EDI integrations) live on the application server's file system (typically Linux/Unix).
You will need:
- An SSH Client (like PuTTY or MobaXterm): To connect to the application server and execute shell scripts (e.g., kicking off a batch job manually for testing).
- An SFTP Client (like WinSCP or FileZilla): To view log files, drop test inbound data files into directories, or extract outbound extracts generated by RMS batches.
Important Directories to Know
Once you SSH into the batch server, you'll typically navigate to the RMS batch home directory (e.g., $MMHOME).
$MMHOME/src: Where the source code for batch scripts lives.$MMHOME/error: Where fatal batch error logs are dumped.$MMHOME/data/in: Where inbound integration files are placed before processing.
5. Key Takeaways
Key Takeaways
- Your primary development tool will be a Database IDE like Oracle SQL Developer.
- Always connect using your personal credentials, and use
ALTER SESSION SET CURRENT_SCHEMAto point to the RMS schema. - Enable DBMS Output to see debug messages from PL/SQL blocks.
- You will need SSH and SFTP access to the application server to run batch jobs and view flat files.
