Tabela MRP_RELIEF_INTERFACE

Dúvidas e discussão sobre Oracle EBS Funcional. Setup, processos, configurações, módulos, dicas, etc
Responder
archive
Rank: OraSauro
Rank: OraSauro
Mensagens: 595
Registrado em: Sex, 02 Dez 2016 7:31 am

Estou num cliente cuja a tabela MRP_RELIEF_INTERFACE tem milhões de registros com status 2.
Não encontrei status 5(processado) e nem status 4(erro).

Alguém sabe o que pode estar acontecendo??
archive
Rank: OraSauro
Rank: OraSauro
Mensagens: 595
Registrado em: Sex, 02 Dez 2016 7:31 am

Ativa o Gerenciador de Planejamento.
archive
Rank: OraSauro
Rank: OraSauro
Mensagens: 595
Registrado em: Sex, 02 Dez 2016 7:31 am

Do MRPTRM:
MRP_RELIEF_INTERFACE is a table which stores information used for master schedule relief. Each entry represents a transaction that affects either a master production or master demand schedule.

Entries are created by WIP and PO via database triggers on the tables WIP_DISCRETE_JOBS and MTL_SUPPLY, respectively.

A row is created everytime a discrete job, purchase order or purchase requisition is created, closed, or modified.

When rows are inserted to MRP_RELIEF_INTERFACE the process_status is set to 2 (waiting to be processed). Relief is performed by MRLSCC, a subroutine of the Planning Manger Worker. This program looks for all rows with a PROCESS_STATUS of 2, a null ERROR_MESSAGE and a null REQUEST_ID. It changes the PROCESS_STATUS of these rows to 3 (in process). The appropriate routine is then called to consume the rows flagged. If schedule consumption fails for a row the PROCESS_STATUS will be changed to 4 (processing error) and an error message will be written to the ERROR_MESSAGE field of the row. If schedule consumption succeeds for a row, the PROCESS_STATUS will be changed to 5. The SOURCE_CODE column can be used to identify third party software for loading the MRP_RELIEF_INTERFACE table. The SOURCE_LINE_ID can be used to show where the imported data came from within the third party software (for example, table_name, field_name).
Então o esquema é rodar o Planning Manager e ver o que acontece. Pede o LOG do concurrent para a infra, e se mesmo assim estiver cabuloso, configura a profile MRP: Debug para "Sim" e com a ajuda do DBA executa o Planning Manager e pede o log completo do programa.

Depois fala pra gente o que deu.
archive
Rank: OraSauro
Rank: OraSauro
Mensagens: 595
Registrado em: Sex, 02 Dez 2016 7:31 am

Obrigado.
Vou providenciar a execução do Planning Manager e verificar o log!
Responder
  • Informação
  • Quem está online

    Usuários navegando neste fórum: Nenhum usuário registrado e 10 visitantes