| Questions |
Resolutions |
| What makes FUT tagged batches in SBM switch to ERR tagged batches?
How can you change them back? |
An SBM batch is tagged as FUT when the effective date on the batch is in
the future. A batch in SBM is tagged as ERR whenever there is an
error in the batch header, even if the batch is future dated. If a
user changes and releases an FUT tagged batch and the change creates a
batch header error, this error will cause the batch to be tagged as ERR
when it is re-posted to SBM. You cannot change an ERR tagged batch
back to an FUT tagged batch. |
| We entered a BC document into the NCAS and accidentally keyed the wrong
year in the date field. The batch went to SBM. What's the best
way to fix this batch? |
The effective date needs to be changed on the batch header. The
batch header date is always corrected through GL screen 271. |
| When I tried to change a batch in SBM, I got the
message: "RESOURCE LOCKED BY-APPL:GL ACTIVITY:SBM OPERATOR:
####### TERMINAL:$###". Why does this happen and how do I
unlock the batch so I can correct it? |
SBM batches become "locked up" when a user
accesses an SBM batch through GL screen 271, 272 or 273 and another user
attempts to access the batch through any one of those same screens before
the first user has released the batch from it's edit mode. Changes
to an SBM batch are real-time changes and until the batch records are
released from the change mode, they will remain tied to the first user's
id and terminal number. A batch will become "unlocked" if
the original user properly terminates his/her access to the batch record
prior to exiting the CICS function. If the original user has already
signed off of CICS or is bumped off CICS due to an interruption in the
power source, then the record is locked for the rest of the day and will
not be accessible until after the nightly production run is
processed. The best way to avoid locking an SBM batch is to train
all users with SBM access to properly exit an SBM batch (without leaving a
batch in change or edit mode). |
| I have a balance in my suspense account. When I go to GL screen
220 to look at the entry I need to fix, the entry does not even have a
source code. It is blank! How do I find out what caused the
error if I don't have a source code/audit id? |
NCAS will not allow an unbalanced entry to post to GL. If an
unbalanced transaction tries to post to GL, the system will automatically
create a balancing entry to suspense. No FC audit id is associated
with the transaction because only FC assigns audit id's and the balancing
entry is created after the transaction has left FC and tried to post to
GL. To correct the suspense entry, you must review the Batch Proof
List report for that production run and determine the source of the
entry. The most common reason for a generated suspense entry is the
improper use of accounting rules when keying BC documents. If the
source is AP, look for another generated entry to suspense in a different
company. (Usually this occurs when travel advances/reimbursements
and sales tax/freight prorations are not processed correctly.) |
