Oracle eBusiness Suite R12 (EBS) OBIEE BIP Technical Consultant
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe summarizing role). We have description of role: supporting application of Oracle EBS R12 versions 12.2.6 and 12.2.14. Also mention travel. Also mention location anywhere US. Also mention US persons requirement. Also mention communication methods. Also mention sitting/computer extended periods.
- Responsibilities: The primary responsibility: supporting application of Oracle EBS R12 versions 12.2.6 and 12.2.14. Also maybe travel to client/project location. Also maybe working with business users etc. But we can list responsibilities as bullet list.
- Requirements: Could include required qualifications: Bachelor's degree or equivalent, US persons, location anywhere US, travel, etc. Also maybe experience with one or two Oracle EBS 12.2.x end-to-end implementations, experience with Oracle application framework, BI Technical, RICEF changes - OBIEE (Integrations, Reports changes) and BIP, experience transitioning from OBIEE to OAS/OAC, strong knowledge of system integrations and batch scheduling, hands-on PL/SQL tool and FORMS, good understanding of software engineering practices and various business processes.
- Qualifications: Could separate required vs preferred? The instruction mentions Qualifications as a heading. We could put required qualifications under Requirements and preferred under Qualifications? Or we could combine. But we need to avoid thin sections. Let's think: We have Required Qualifications and Preferred Qualifications in posting. We could make a section "Requirements" for required qualifications, and "Qualifications" for preferred qualifications. Or we could merge them into one "Qualifications" section with subheadings? But we only allowed headings as listed; we cannot add custom headings. So we need to decide which sections to include.
We have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have info for:
- About the role: description of role, location, travel, US persons, communication, sitting/computer.
- Responsibilities: supporting application of Oracle EBS R12 versions 12.2.6 and 12.2.14, travel to client/project location (maybe also responsibility). Could also include working with business users etc (but that's preferred). We'll list bullet points.
- Requirements: Bachelor's degree or equivalent, US persons, location anywhere US, travel requirement, maybe also experience with one or two Oracle EBS 12.2.x end-to-end implementations, experience with Oracle application framework, BI Technical, RICEF changes - OBIEE (Integrations, Reports changes) and BIP, experience transitioning from OBIEE to OAS/OAC, strong knowledge of system integrations and batch scheduling, hands-on PL/SQL tool and FORMS, good understanding of software engineering practices and various business processes.
- Qualifications (preferred): Strong Understanding of EBS modules to support upgrades, functional testing and defect fixes. Experience and desire to work closely with business users and techno-functional team.
- Skills: Could list specific technical skills: Oracle EBS R12, OBIEE, BIP, BI Technical, RICEF changes, PL/SQL, FORMS, System Integrations, Batch scheduling, OAS, OAC, software engineering practices, business processes, communication tools (Teams, Telephone, Email, Face-to-Face). But many of these overlap with requirements. Might be thin. Perhaps we can omit Skills if not enough distinct content. But we need to decide.
- Benefits: list as given.
- Pay: compensation ranges.
- Schedule: Not mentioned explicitly; maybe we can omit because no schedule info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we should not include Schedule if not stated. So we omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only, no /. Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting that are relevant.
Let's extract details precisely.
About the role:
- Infosys is seeking Oracle eBusiness Suite R12 (EBS) OBIEE consultant with knowledge and experience in RICEF Changes – OBIEE, BIP and BI Technical.
- The position will primarily be responsible for supporting application of Oracle EBS R12 versions 12.2.6 and 12.2.14.
- Location for this position is Anywhere in the US.
- This position may require travel to client/project location.
- In order to comply with legal requirements, this role is limited to “U.S. persons” as defined by 22 C.F.R.120.15. U.S. persons include U.S. citizens, U.S. Lawful Permanent Residents, and certain refugees and asylees.
- Candidates should be able to effectively communicate by Microsoft Teams, Telephone, Email, and Face-to-Face.
- The job may also entail sitting as well as working at a computer for extended periods of time.
We could also mention Bachelor's degree etc but that's more requirement.
Responsibilities:
- Supporting application of Oracle EBS R12 versions 12.2.6 and 12.2.14.
- Travel to client/project location (as needed).
- Possibly working with business users and techno-functional team? That's preferred qualification. Might be responsibility but we can keep under qualifications.
We'll list responsibilities as bullet list.
Requirements:
- Bachelor’s degree or foreign equivalent required from an accredited institution.
- Will also consider three years of progressive experience in the specialty in lieu of every year of education.
- Experience with one or two Oracle EBS 12.2.x end-to-end implementations.
- Experience working in the Oracle application framework, BI Technical, RICEF changes - OBIEE (Integrations, Reports changes) and BIP.
- Experience transitioning from OBIEE to Oracle Analytics Server (OAS) and Oracle Analytics Cloud (OAC) technology.
- Strong knowledge of System Integrations and Batch scheduling.
- Hands-on PL/SQL tool and FORMS.
- Good understanding of software engineering practices and various business processes.
- Location: Anywhere in the US (maybe already mentioned).
- Must be a U.S. person (citizen, lawful permanent resident, refugee/asylee) per 22 C.F.R.120.15.
- Willingness to travel to client/project location.
Qualifications (preferred):
- Strong Understanding of EBS modules to support upgrades, functional testing and defect fixes.
- Experience and desire to work closely with business users and techno-functional team.
Benefits:
- Medical/Dental/Vision/Life Insurance
- Long-term/Short-term Disability
- Health and Dependent Care Reimbursement Accounts
- Insurance (Accident, Critical Illness, Hospital Indemnity, Legal)
- 401(k) plan and contributions dependent on salary level
- Paid holidays plus Paid Time Off
Pay:
- Estimated annual compensation range:
- In CA / CO / IL / MA / MD / MN / NJ / NY / VA / VT / WA: $73,000 to $102,200
- In Washington, DC: $66,100 to $100,200
We should not repeat benefits duplicate.
Now produce HTML.
We need to wrap each section in
heading, then content.
For About the role: we can use
paragraphs.
For Responsibilities:
- ...
For Requirements:
- ...
For Qualifications:
- ...
For Benefits:
- ...
For Pay: maybe
with details.
Make sure not to include any extra text outside HTML.
Let's craft.
Check for any boilerplate: We removed EEO, About Us (maybe we could include under About the role? But About Us is company description; not required. We can omit as it's not about the role. The instruction: include a section ONLY when the posting has real, specific content for it. About Us is not about the role; but we could treat as About the role? Better to omit About Us because it's not role-specific. The posting includes "About Us" but we can ignore as it's boilerplate? It's not legal/EEO but it's company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not listed but could
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting that are relevant. Let's extract details precisely. About the role: - Infosys is seeking Oracle eBusiness Suite R12 (EBS) OBIEE consultant with knowledge and experience in RICEF Changes – OBIEE, BIP and BI Technical. - The position will primarily be responsible for supporting application of Oracle EBS R12 versions 12.2.6 and 12.2.14. - Location for this position is Anywhere in the US. - This position may require travel to client/project location. - In order to comply with legal requirements, this role is limited to “U.S. persons” as defined by 22 C.F.R.120.15. U.S. persons include U.S. citizens, U.S. Lawful Permanent Residents, and certain refugees and asylees. - Candidates should be able to effectively communicate by Microsoft Teams, Telephone, Email, and Face-to-Face. - The job may also entail sitting as well as working at a computer for extended periods of time. We could also mention Bachelor's degree etc but that's more requirement. Responsibilities: - Supporting application of Oracle EBS R12 versions 12.2.6 and 12.2.14. - Travel to client/project location (as needed). - Possibly working with business users and techno-functional team? That's preferred qualification. Might be responsibility but we can keep under qualifications. We'll list responsibilities as bullet list. Requirements: - Bachelor’s degree or foreign equivalent required from an accredited institution. - Will also consider three years of progressive experience in the specialty in lieu of every year of education. - Experience with one or two Oracle EBS 12.2.x end-to-end implementations. - Experience working in the Oracle application framework, BI Technical, RICEF changes - OBIEE (Integrations, Reports changes) and BIP. - Experience transitioning from OBIEE to Oracle Analytics Server (OAS) and Oracle Analytics Cloud (OAC) technology. - Strong knowledge of System Integrations and Batch scheduling. - Hands-on PL/SQL tool and FORMS. - Good understanding of software engineering practices and various business processes. - Location: Anywhere in the US (maybe already mentioned). - Must be a U.S. person (citizen, lawful permanent resident, refugee/asylee) per 22 C.F.R.120.15. - Willingness to travel to client/project location. Qualifications (preferred): - Strong Understanding of EBS modules to support upgrades, functional testing and defect fixes. - Experience and desire to work closely with business users and techno-functional team. Benefits: - Medical/Dental/Vision/Life Insurance - Long-term/Short-term Disability - Health and Dependent Care Reimbursement Accounts - Insurance (Accident, Critical Illness, Hospital Indemnity, Legal) - 401(k) plan and contributions dependent on salary level - Paid holidays plus Paid Time Off Pay: - Estimated annual compensation range: - In CA / CO / IL / MA / MD / MN / NJ / NY / VA / VT / WA: $73,000 to $102,200 - In Washington, DC: $66,100 to $100,200 We should not repeat benefits duplicate. Now produce HTML. We need to wrap each section in
heading, then content. For About the role: we can use
paragraphs. For Responsibilities:
- ...
For Requirements:
- ...
For Qualifications:
- ...
For Benefits:
- ...
For Pay: maybe
with details. Make sure not to include any extra text outside HTML. Let's craft. Check for any boilerplate: We removed EEO, About Us (maybe we could include under About the role? But About Us is company description; not required. We can omit as it's not about the role. The instruction: include a section ONLY when the posting has real, specific content for it. About Us is not about the role; but we could treat as About the role? Better to omit About Us because it's not role-specific. The posting includes "About Us" but we can ignore as it's boilerplate? It's not legal/EEO but it's company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not listed but could
- ...
For Pay: maybe
- ...
For Benefits:
- ...
For Qualifications:
- ...
For Requirements: