$(function () { pageContext.i18n.modTalk = 'moderation talk'; pageContext.i18n.replyToComment = 'Reply'; pageContext.i18n.modTalkEmpty = 'moderation talk is empty'; pageContext.url.getModTalk = "/comments/%25ID%25/listModTalk.json"; pageContext.url.possibleCommentRecipients = "/comments/%ID%/possibleRecipients.json"; pageContext.url.commentEdit = '/comments/%25ID%25/edit.html'; pageContext.url.commentView = '/comments/%ID%/view.html'; pageContext.i18n.commentVisibility = { 'full': 'Viewable by all users', 'op': 'Viewable by the original poster', 'mod': 'Viewable by moderators', 'opAndMod': 'Viewable by moderators and the original poster', 'other': 'Advanced visibility', 'dialogTitle': 'Comment visibility', 'selectGroups': 'Visible to groups', 'selectOther': 'Other recipients', 'selectOriginalPoster': 'Original poster', 'selectModerators': 'Moderators', 'selectAssignees': 'Asked to answer users' }; pageContext.i18n.commentMenuLabels = { 'comment-edit': 'comments.menu.edit', 'comment-delete': 'comments.menu.delete', 'comment-convert': 'comments.menu.convert' };pageContext.i18n.answer= { bestAnswer: 'Best Answer', controlBar : { accept: 'Accept', unaccept: 'Unaccept', acceptCommand: 'Accept this answer as correct', cancelAcceptedCommand: 'Remove this answers accepted status' } }; window.croles = { u: false, op: false, m: false, og: false, as: false, ag: false, dc: false, doc: false, eo: false, ea: false }; tools.init({ q: { e: false, ew: false, eo: false, r: false, ro: false, d: false, dow: false, fv: false, c: false, co: false, p: false, tm: false , ms: false, mos: false }, n: { f: false, vf: false, vfo: false, vr: false, vro: false, c: false, co: false, vu: false, vd: false, w: false, wo: false, l: false }, c: { e: false, eo: false, d: false, dow: false, ta: false, tao: false, l: false }, a: { e: false, ew: false, eo: false, d: false, dow: false, a: false, aoq: false, ao: false, tc: false, tco: false, p: false, tm: false }, pc: croles }, { tc: true, nsc: true }); commandUtils.initializeLabels(); }); Skip to Content
avatar image
Former Member

Planned order getting stuck while CIFing , what is the remedy???

Dear Experts,

CIF queue error: Planned Order xxxxx version N002 is not valid

CIF stuck queues with status RETRY. "Command to tRFC/qRFC: Execute LUW again

the issue here is planned order is getting stuck and isn't moving, what would I do to make it move ..

I can think of changing the validity date of PV ,

apart from that can you think of any other solution

Thanks

Rahul Ohio

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    Nov 08, 2016 at 12:06 PM

    Hi Rahul,

    If the queue is stuck with the error message "Planned Order xxxxx version N002 is not valid on the finish date xx.xx.xxxx", the PV validity needs to be adjusted such that it is valid on that date.

    Other than that, you may double click the error message in the stuck queue to go to log display screen and see if any other error message has been raised during order transfer.

    Regards,
    Tiago

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 10, 2016 at 05:05 AM
    Thanks Tiago
    Add comment
    10|10000 characters needed characters exceeded

  • Nov 14, 2016 at 11:48 AM

    HI Rahul,

    Before changing the validity date of the production version, please also check the validity of the BOM that is involved within the production version. Is it really valid in or out of the PV validity date? This also may cause the error. After confirming the validity dates of the BOM , then you may considering changing the validity dates of the production version.

    This should help

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 25, 2017 at 05:56 PM

    Hello Tiago

    ALL comes with a validity date -BOM,PV,Planned order,Material,PDS,sales order-

    Is there any single tcode owning ( an editable screen ) that lists all Masters and transaction data in ECC carrying From : validity date and To: Validity date

    so that I can alter the validity date,--in one go --in one single screen.minimizing validity issues while CIFing to APO

    The reason behind is I am into CIFing Masters and transaction data,to APO via PDS- most often I come across this validity error.hampering my continuity. OR can you please list out all tcodes from your memory -where do I find this validity date stuff( in which screen) -to do the validity editing stuff.

    In essence the point I am trying to make is -validity date stuff is spread across the entire ECC system here and there- I wish -one stop shop(in the form of tcode/Single Screen-encompassing all validity stuff(editable mode) for all Masters and Transaction.data

    I am not sure I am talking sense,but if you find I have a point your inputs would make my job easy.

    Thanks

    Rahul Ohio

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 27, 2017 at 11:53 PM

    Hello Rahul,

    Regarding the "Command to tRFC/qRFC: Execute LUW again" error queues, these are generated due to existent locks during the processing of the queue.

    Maybe, if there are parallel processes been executed, if they interact with the same object (orders, documents, master data...), you could be locking the object in one process while trying to process the same object in another process.

    I would suggest you to review if there are parallel processes running when these queues appear in your system.

    Regards,

    Arthur Braga

    Add comment
    10|10000 characters needed characters exceeded