1. A dynamic-web-services-server-implemented method for publishing a dynamic web service, the method comprising: receiving, by said dynamic-web-services server from a first enterprise-resource-planning client, a recorded transaction map describing a recorded transaction between said first enterprise-resource-planning client and an enterprise-resource-planning server, said recorded transaction map including metadata corresponding to a plurality of transaction fields; generating, by said dynamic-web-services server, a service description framework for a new dynamic web service corresponding to said recorded transaction, including for each of said plurality of transaction fields, defining an input corresponding to the current transaction field and storing said defined input in said service description framework; determining, by said dynamic-web-services server, a unique service identifier for invoking said new dynamic web service; persisting, by said dynamic-web-services server, said unique service identifier, said service description framework, and said recorded transaction map in a data store; receiving, by said dynamic-web-services server, a first request from said first enterprise-resource-planning client or a second enterprise-resource-planning client to invoke said new dynamic web service according to a package of input data, said first request indicating said unique service identifier, said package of input data being received in a first format according to a first calling mechanism; retrieving, by said dynamic-web-services server, said recorded transaction map from said data store according to said unique service identifier; according to said recorded transaction map, determining, by said dynamic-web-services server, at least one Enterprise Application API call for performing said recorded transaction, said at least one Enterprise Application API call requiring a second calling mechanism, different from said first calling mechanism; repackaging, by said dynamic-web-services server, said package of input data in said first format into repackaged input data in a second format that complies with said second calling mechanism; using said at least one Enterprise Application API call, invoking, by said dynamic-web-services server, a remote Enterprise Application server to perform said recorded transaction according to said second calling mechanism, said at least one Enterprise Application API call, and said repackaged input data; and receiving from said enterprise-resource-planning server process output data corresponding to the invocation of said enterprise-resource-planning server.